Listening on IPv6 address

List overview All Threads
Download

newer

older

各个费用

obsolete rundir

Leoš Bitto

3 Čen 2013 3 Čen '13

23:22

Hello, it seems that knotd suffers from the same issue as described here: http://lists.scusting.com/index.php?t=msg&th=244420 I have Debian 7.0 with http://deb.knot-dns.cz/debian/dists/wheezy/main/binary-i386/net/knot_1.2.0-… and this is in /var/log/syslog after reboot: Jun 3 22:37:43 ns knot[2091]: Binding to interface 2xxx:xxxx:xxxx:xxxx::1 port 53. Jun 3 22:37:43 ns knot[2091]: [error] Cannot bind to socket (errno 99). Jun 3 22:37:43 ns knot[2091]: [error] Could not bind to UDP interface 2xxx:xxxx:xxxx:xxxx::1 port 53. I have a static IPv6 address configured in /etc/network/interfaces. Restarting knot later binds to this IPv6 address without any problem - it is only the first start which fails (during OS booting). What do you think that is the proper way of making knotd reliably listen on a static IPv6 address? I would prefer if I could avoid restarting knotd. Leos Bitto

Attachments:

attachment.html (text/html — 1,3 KB)

Show replies by date

Leoš Bitto

4 Čen 4 Čen

0:49

On Mon, Jun 3, 2013 at 11:22 PM, Leoš Bitto <leos.bitto(a)gmail.com> wrote:

...

I don't really like replying to myself, but just in case anybody is interested - the following hack makes it work for me: echo "while ip -6 addr | grep -q tentative; do sleep 1; done"

...

> /etc/default/knotd

Maybe that it would be better if knotd could do this internally. Leoš Bitto

Leoš Bitto

9 Čec 9 Čec

9:32

On Tue, Jun 4, 2013 at 12:49 AM, Leoš Bitto <leos.bitto(a)gmail.com> wrote:

...

On Mon, Jun 3, 2013 at 11:22 PM, Leoš Bitto <leos.bitto(a)gmail.com> wrote:

Hello, it seems that knotd suffers from the same issue as described here: http://lists.scusting.com/index.php?t=msg&th=244420 I have Debian 7.0 with http://deb.knot-dns.cz/debian/dists/wheezy/main/binary-i386/net/knot_1.2.0-… installed and this is in /var/log/syslog after reboot: Jun 3 22:37:43 ns knot[2091]: Binding to interface 2xxx:xxxx:xxxx:xxxx::1 port 53. Jun 3 22:37:43 ns knot[2091]: [error] Cannot bind to socket (errno 99). Jun 3 22:37:43 ns knot[2091]: [error] Could not bind to UDP interface 2xxx:xxxx:xxxx:xxxx::1 port 53. I have a static IPv6 address configured in /etc/network/interfaces. Restarting knot later binds to this IPv6 address without any problem - it is only the first start which fails (during OS booting). What do you think that is the proper way of making knotd reliably listen on a static IPv6 address? I would prefer if I could avoid restarting knotd.

I don't really like replying to myself, but just in case anybody is interested - the following hack makes it work for me: echo "while ip -6 addr | grep -q tentative; do sleep 1; done" >> /etc/default/knotd

One more reply to myself: after upgrading from knotd 1.2.0 to 1.3.0-rc3 the file /etc/default/knotd is ignored (bug?), so I had to take a different approach: in /etc/network/interfaces I have added "pre-up sysctl net.ipv6.conf.eth0.dad_transmits=0" after "iface eth0 inet6 static" and it seems to work fine so far. Leoš Bitto

Ondřej Surý

9:38

On 9. 7. 2013, at 9:32, Leoš Bitto <leos.bitto(a)gmail.com> wrote:

...

One more reply to myself: after upgrading from knotd 1.2.0 to 1.3.0-rc3 the file /etc/default/knotd is ignored (bug?)

Nope, I have dropped the /etc/default/knotd all-together, but the packages might miss the dpkg-maintscript-helper rm_conffile stanzas in maintainer scripts.

...

so I had to take a different approach: in /etc/network/interfaces I have added "pre-up sysctl net.ipv6.conf.eth0.dad_transmits=0" after "iface eth0 inet6 static" and it seems to work fine so far.

Thanks for the note. I'll open an issue for this so we don't forget to discuss what to do with the tentative-ipv6 issue for Knot 1.3.0. O. -- Ondřej Surý -- Chief Science Officer ------------------------------------------- CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC Americka 23, 120 00 Praha 2, Czech Republic mailto:ondrej.sury@nic.cz http://nic.cz/ tel:+420.222745110 fax:+420.222745112 -------------------------------------------

Ondřej Surý

9:51

On 9. 7. 2013, at 9:38, Ondřej Surý <ondrej.sury(a)nic.cz> wrote:

...

so I had to take a different approach: in /etc/network/interfaces I have added "pre-up sysctl net.ipv6.conf.eth0.dad_transmits=0" after "iface eth0 inet6 static" and it seems to work fine so far.

Thanks for the note. I'll open an issue for this so we don't forget to discuss what to do with the tentative-ipv6 issue for Knot 1.3.0.

https://gitlab.labs.nic.cz/knot/issues/72 O. -- Ondřej Surý -- Chief Science Officer ------------------------------------------- CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC Americka 23, 120 00 Praha 2, Czech Republic mailto:ondrej.sury@nic.cz http://nic.cz/ tel:+420.222745110 fax:+420.222745112 -------------------------------------------

Ondřej Surý

4 Čen 4 Čen

10:05

Could we adapt: http://lists.scusting.com/index.php?t=msg&th=244420&goto=1042086&am…

...

For IPv6 the IPV6_PKTINFO socket option described in RFC 3542 allows applications to get and set the local address per-packet; this is hopefully implemented on most Unix-like systems.

to 1.3.0? That way we would be able to bind to 0/0 and still be able to control the src address on outgoing packets.

...

For IPv4, Linux has a similar IP_PKTINFO option whereas BSD and Solaris provide the options IP_{RECVDST,SENDSRC}ADDR. This lack of portability may explain why more applications have not adopted this approach yet.

This might also be doable with right autoconf magic detecting the right options at compile time. O. On 3. 6. 2013, at 23:22, Leoš Bitto <leos.bitto(a)gmail.com> wrote:

...

Hello, it seems that knotd suffers from the same issue as described here: http://lists.scusting.com/index.php?t=msg&th=244420 I have Debian 7.0 with http://deb.knot-dns.cz/debian/dists/wheezy/main/binary-i386/net/knot_1.2.0-… installed and this is in /var/log/syslog after reboot: Jun 3 22:37:43 ns knot[2091]: Binding to interface 2xxx:xxxx:xxxx:xxxx::1 port 53. Jun 3 22:37:43 ns knot[2091]: [error] Cannot bind to socket (errno 99). Jun 3 22:37:43 ns knot[2091]: [error] Could not bind to UDP interface 2xxx:xxxx:xxxx:xxxx::1 port 53. I have a static IPv6 address configured in /etc/network/interfaces. Restarting knot later binds to this IPv6 address without any problem - it is only the first start which fails (during OS booting). What do you think that is the proper way of making knotd reliably listen on a static IPv6 address? I would prefer if I could avoid restarting knotd. Leos Bitto _______________________________________________ knot-dns-users mailing list knot-dns-users(a)lists.nic.cz https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users

Leoš Bitto

11:08

That could be nice, but please allow explicit binding as well. Currently I have a recursive caching resolver bound to ::1 and knotd to the external interface and I would like to be able to keep this setup. On Tue, Jun 4, 2013 at 10:05 AM, Ondřej Surý <ondrej.sury(a)nic.cz> wrote:

...

Could we adapt: http://lists.scusting.com/index.php?t=msg&th=244420&goto=1042086&am…

For IPv6 the IPV6_PKTINFO socket option described in RFC 3542 allows applications to get and set the local address per-packet; this is hopefully implemented on most Unix-like systems.

to 1.3.0? That way we would be able to bind to 0/0 and still be able to control the src address on outgoing packets.

This might also be doable with right autoconf magic detecting the right options at compile time. O. On 3. 6. 2013, at 23:22, Leoš Bitto <leos.bitto(a)gmail.com> wrote:

Hello, it seems that knotd suffers from the same issue as described here: http://lists.scusting.com/index.php?t=msg&th=244420 I have Debian 7.0 with http://deb.knot-dns.cz/debian/dists/wheezy/main/binary-i386/net/knot_1.2.0-… installed and this is in /var/log/syslog after reboot: Jun 3 22:37:43 ns knot[2091]: Binding to interface 2xxx:xxxx:xxxx:xxxx::1 port 53. Jun 3 22:37:43 ns knot[2091]: [error] Cannot bind to socket (errno 99). Jun 3 22:37:43 ns knot[2091]: [error] Could not bind to UDP interface 2xxx:xxxx:xxxx:xxxx::1 port 53. I have a static IPv6 address configured in /etc/network/interfaces. Restarting knot later binds to this IPv6 address without any problem - it is only the first start which fails (during OS booting). What do you think that is the proper way of making knotd reliably listen on a static IPv6 address? I would prefer if I could avoid restarting knotd. Leos Bitto _______________________________________________ knot-dns-users mailing list knot-dns-users(a)lists.nic.cz https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users

-- Ondřej Surý -- Chief Science Officer ------------------------------------------- CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC Americka 23, 120 00 Praha 2, Czech Republic mailto:ondrej.sury@nic.cz http://nic.cz/ tel:+420.222745110 fax:+420.222745112 ------------------------------------------- _______________________________________________ knot-dns-users mailing list knot-dns-users(a)lists.nic.cz https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users

4100

days inactive

4136

days old

knot-dns-users@lists.nic.cz

Manage subscription

6 comments

2 participants

tags (0)

participants (2)

Leoš Bitto
Ondřej Surý