ntpd bind() failure: Can't assign requested address

classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|

ntpd bind() failure: Can't assign requested address

Melanie Schulte
Hi!

[First of all, I have posted this question already on the FreeBSD
forum -- so far without replies -- and now my hope is that the set of
subscribers here and those of the forum do not completely coincide.]

I have installed FreeBSD 9.1 on my server (it's a virtualized qemu/kvm
environment, in case that matters) and during boot the following
messages appear:

    ntpd[766]: ntpd 4.2.4p5-a (1)
    ntpd[767]: bind() fd 23, family AF_INET6, port 123, scope 2, addr fe80::216:36ff:fe74:2076, mcast=0 flags=0x11 fails: Can't assign requested address
    ntpd[767]: unable to create socket on re0 (3) for fe80::216:36ff:fe74:2076#123

This happens with a GENERIC kernel. I have not touched any IPv6
related configuration after install, so everything should be in the
default state. Neither have I changed the ntp/ntpd configuration.

Although I could find some threads where people were discussing the
same problem, none of the mentioned suggestions fixed this for me.

In particular I tried setting

    ipv6_activate_all_interfaces="YES"

in rc.conf -- didn't fix the problem.

According to ifconfig, my interfaces, re0 in particular, have IPv6
addresses associated to them. So why would it fail that a process
tries to bind to it? Note that I'm rather unexperienced wrt IPv6.

Would be great if somebody could give me a hint into the right
direction. Anybody else experiencing this? Thank you very much!

~ melanie
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Damien Fleuriot-2

On 12 Mar 2013, at 22:42, "M. Schulte" <[hidden email]> wrote:

> Hi!
>
> [First of all, I have posted this question already on the FreeBSD
> forum -- so far without replies -- and now my hope is that the set of
> subscribers here and those of the forum do not completely coincide.]
>
> I have installed FreeBSD 9.1 on my server (it's a virtualized qemu/kvm
> environment, in case that matters) and during boot the following
> messages appear:
>
>   ntpd[766]: ntpd 4.2.4p5-a (1)
>   ntpd[767]: bind() fd 23, family AF_INET6, port 123, scope 2, addr fe80::216:36ff:fe74:2076, mcast=0 flags=0x11 fails: Can't assign requested address
>   ntpd[767]: unable to create socket on re0 (3) for fe80::216:36ff:fe74:2076#123
>
> This happens with a GENERIC kernel. I have not touched any IPv6
> related configuration after install, so everything should be in the
> default state. Neither have I changed the ntp/ntpd configuration.
>
> Although I could find some threads where people were discussing the
> same problem, none of the mentioned suggestions fixed this for me.
>
> In particular I tried setting
>
>   ipv6_activate_all_interfaces="YES"
>
> in rc.conf -- didn't fix the problem.
>
> According to ifconfig, my interfaces, re0 in particular, have IPv6
> addresses associated to them. So why would it fail that a process
> tries to bind to it? Note that I'm rather unexperienced wrt IPv6.
>
> Would be great if somebody could give me a hint into the right
> direction. Anybody else experiencing this? Thank you very much!
>
> ~ melanie
>

I'll check tomorrow if we have the same issue at work, although it doesn't look familiar.

We've got a 9.1 with a custom kernel (although nothing related to ipv6 changed) running in KVM.
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Kevin Oberman-4
In reply to this post by Melanie Schulte
On Tue, Mar 12, 2013 at 2:42 PM, M. Schulte <[hidden email]> wrote:

> Hi!
>
> [First of all, I have posted this question already on the FreeBSD
> forum -- so far without replies -- and now my hope is that the set of
> subscribers here and those of the forum do not completely coincide.]
>
> I have installed FreeBSD 9.1 on my server (it's a virtualized qemu/kvm
> environment, in case that matters) and during boot the following
> messages appear:
>
>    ntpd[766]: ntpd 4.2.4p5-a (1)
>    ntpd[767]: bind() fd 23, family AF_INET6, port 123, scope 2, addr
> fe80::216:36ff:fe74:2076, mcast=0 flags=0x11 fails: Can't assign requested
> address
>    ntpd[767]: unable to create socket on re0 (3) for
> fe80::216:36ff:fe74:2076#123
>
> This happens with a GENERIC kernel. I have not touched any IPv6
> related configuration after install, so everything should be in the
> default state. Neither have I changed the ntp/ntpd configuration.
>
> Although I could find some threads where people were discussing the
> same problem, none of the mentioned suggestions fixed this for me.
>
> In particular I tried setting
>
>    ipv6_activate_all_interfaces="**YES"
>
> in rc.conf -- didn't fix the problem.
>
> According to ifconfig, my interfaces, re0 in particular, have IPv6
> addresses associated to them. So why would it fail that a process
> tries to bind to it? Note that I'm rather unexperienced wrt IPv6.
>
> Would be great if somebody could give me a hint into the right
> direction. Anybody else experiencing this? Thank you very much!
>
> ~ melanie
>

 What is the address space is the address you are seeing on the interface?
Is it is a link-local address or one assigned by the router, a static from
rc.conf or DHCPv6? You should have two inet6 addresses, one is link-local
(starts with "fe") and another should start with "2". There may be more
than two.
--
R. Kevin Oberman, Network Engineer
E-mail: [hidden email]
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Damien Fleuriot-2
In reply to this post by Damien Fleuriot-2

On Mar 12, 2013, at 11:44 PM, Damien Fleuriot <[hidden email]> wrote:

>
> On 12 Mar 2013, at 22:42, "M. Schulte" <[hidden email]> wrote:
>
>> Hi!
>>
>> [First of all, I have posted this question already on the FreeBSD
>> forum -- so far without replies -- and now my hope is that the set of
>> subscribers here and those of the forum do not completely coincide.]
>>
>> I have installed FreeBSD 9.1 on my server (it's a virtualized qemu/kvm
>> environment, in case that matters) and during boot the following
>> messages appear:
>>
>>  ntpd[766]: ntpd 4.2.4p5-a (1)
>>  ntpd[767]: bind() fd 23, family AF_INET6, port 123, scope 2, addr fe80::216:36ff:fe74:2076, mcast=0 flags=0x11 fails: Can't assign requested address
>>  ntpd[767]: unable to create socket on re0 (3) for fe80::216:36ff:fe74:2076#123
>>
>> This happens with a GENERIC kernel. I have not touched any IPv6
>> related configuration after install, so everything should be in the
>> default state. Neither have I changed the ntp/ntpd configuration.
>>
>> Although I could find some threads where people were discussing the
>> same problem, none of the mentioned suggestions fixed this for me.
>>
>> In particular I tried setting
>>
>>  ipv6_activate_all_interfaces="YES"
>>
>> in rc.conf -- didn't fix the problem.
>>
>> According to ifconfig, my interfaces, re0 in particular, have IPv6
>> addresses associated to them. So why would it fail that a process
>> tries to bind to it? Note that I'm rather unexperienced wrt IPv6.
>>
>> Would be great if somebody could give me a hint into the right
>> direction. Anybody else experiencing this? Thank you very much!
>>
>> ~ melanie
>>
>
> I'll check tomorrow if we have the same issue at work, although it doesn't look familiar.
>
> We've got a 9.1 with a custom kernel (although nothing related to ipv6 changed) running in KVM.


I confirm I have the same issue on 9.1 r247912 , as below:

Clearing /tmp (X related).
Updating motd:.
Starting ntpd.
Mar  8 14:57:23 pf1-drt ntpd[938]: bind() fd 23, family AF_INET6, port 123, scope 2, addr fe80::90bd:54ff:fe55:2d21, mcast=0 flags=0x11 fails: Can't assign requested address
Mar  8 14:57:23 pf1-drt ntpd[938]: unable to create socket on vlan12 (3) for fe80::90bd:54ff:fe55:2d21#123



However, ntpd runs fine and is bound to the following addresses:

root@pf1-drt:/var/run # sockstat | grep ntp
root     ntpd       938   3  dgram  -> /var/run/logpriv
root     ntpd       938   20 udp4   *:123                 *:*
root     ntpd       938   21 udp6   *:123                 *:*
root     ntpd       938   22 udp4   195.158.240.37:123    *:*
root     ntpd       938   23 udp4   192.168.32.253:123    *:*
root     ntpd       938   24 udp6   fe80:3::a8b0:eeff:fef9:dbb:123 *:*
root     ntpd       938   25 udp4   192.168.22.254:123    *:*
root     ntpd       938   26 udp6   fe80:4::6820:e3ff:fe0b:76dc:123 *:*
root     ntpd       938   27 udp6   ::1:123               *:*
root     ntpd       938   28 udp6   fe80:7::1:123         *:*
root     ntpd       938   29 udp4   127.0.0.1:123         *:*
root     ntpd       938   31 udp6   fe80:2::90bd:54ff:fe55:2d21:123 *:*
root     ntpd       938   32 udp4   192.168.22.253:123    *:*

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Schrodinger
On 2013/03/13 14:38, Fleuriot Damien wrote:

>
> On Mar 12, 2013, at 11:44 PM, Damien Fleuriot <[hidden email]> wrote:
>
> >
> > On 12 Mar 2013, at 22:42, "M. Schulte" <[hidden email]> wrote:
> >
> >> Hi!
> >>
> >> [First of all, I have posted this question already on the FreeBSD
> >> forum -- so far without replies -- and now my hope is that the set of
> >> subscribers here and those of the forum do not completely coincide.]
> >>
> >> I have installed FreeBSD 9.1 on my server (it's a virtualized qemu/kvm
> >> environment, in case that matters) and during boot the following
> >> messages appear:
> >>
> >>  ntpd[766]: ntpd 4.2.4p5-a (1)
> >>  ntpd[767]: bind() fd 23, family AF_INET6, port 123, scope 2, addr fe80::216:36ff:fe74:2076, mcast=0 flags=0x11 fails: Can't assign requested address
> >>  ntpd[767]: unable to create socket on re0 (3) for fe80::216:36ff:fe74:2076#123
> >>
> >> This happens with a GENERIC kernel. I have not touched any IPv6
> >> related configuration after install, so everything should be in the
> >> default state. Neither have I changed the ntp/ntpd configuration.
> >>
> >> Although I could find some threads where people were discussing the
> >> same problem, none of the mentioned suggestions fixed this for me.
> >>
> >> In particular I tried setting
> >>
> >>  ipv6_activate_all_interfaces="YES"
> >>
> >> in rc.conf -- didn't fix the problem.
> >>
> >> According to ifconfig, my interfaces, re0 in particular, have IPv6
> >> addresses associated to them. So why would it fail that a process
> >> tries to bind to it? Note that I'm rather unexperienced wrt IPv6.
> >>
> >> Would be great if somebody could give me a hint into the right
> >> direction. Anybody else experiencing this? Thank you very much!
> >>
> >> ~ melanie
> >>
> >
> > I'll check tomorrow if we have the same issue at work, although it doesn't look familiar.
> >
> > We've got a 9.1 with a custom kernel (although nothing related to ipv6 changed) running in KVM.
>
>
> I confirm I have the same issue on 9.1 r247912 , as below:
>
> Clearing /tmp (X related).
> Updating motd:.
> Starting ntpd.
> Mar  8 14:57:23 pf1-drt ntpd[938]: bind() fd 23, family AF_INET6, port 123, scope 2, addr fe80::90bd:54ff:fe55:2d21, mcast=0 flags=0x11 fails: Can't assign requested address
> Mar  8 14:57:23 pf1-drt ntpd[938]: unable to create socket on vlan12 (3) for fe80::90bd:54ff:fe55:2d21#123
>
>
>
> However, ntpd runs fine and is bound to the following addresses:
>
> root@pf1-drt:/var/run # sockstat | grep ntp
> root     ntpd       938   3  dgram  -> /var/run/logpriv
> root     ntpd       938   20 udp4   *:123                 *:*
> root     ntpd       938   21 udp6   *:123                 *:*
> root     ntpd       938   22 udp4   195.158.240.37:123    *:*
> root     ntpd       938   23 udp4   192.168.32.253:123    *:*
> root     ntpd       938   24 udp6   fe80:3::a8b0:eeff:fef9:dbb:123 *:*
> root     ntpd       938   25 udp4   192.168.22.254:123    *:*
> root     ntpd       938   26 udp6   fe80:4::6820:e3ff:fe0b:76dc:123 *:*
> root     ntpd       938   27 udp6   ::1:123               *:*
> root     ntpd       938   28 udp6   fe80:7::1:123         *:*
> root     ntpd       938   29 udp4   127.0.0.1:123         *:*
> root     ntpd       938   31 udp6   fe80:2::90bd:54ff:fe55:2d21:123 *:*
> root     ntpd       938   32 udp4   192.168.22.253:123    *:*
>
> _______________________________________________
> [hidden email] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "[hidden email]"
I have observed the same behaviour :

Mar 13 14:10:27 howard ntpd[1603]: bind() fd 32, family AF_INET6, port 123, scope 9, addr fe80::20a:faff:fe20:3a1, mcast=0 flags=0x13 fails: Can't assign requested address
Mar 13 14:10:27 howard ntpd[1603]: unable to create socket on gif6 (3994) for fe80::20a:faff:fe20:3a1#123

FreeBSD howard.tog.space 9.1-STABLE FreeBSD 9.1-STABLE #1: Mon Feb 25 18:37:43 GMT 2013     [hidden email]:/usr/obj/usr/src/sys/HOWARD  amd64

# sockstat -lp123
USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS      
root     ntpd       1603  20 udp4   *:123                 *:*
root     ntpd       1603  21 udp6   *:123                 *:*
root     ntpd       1603  22 udp4   87.198.63.241:123     *:*
root     ntpd       1603  23 udp4   192.168.1.2:123       *:*
root     ntpd       1603  24 udp4   172.16.0.1:123        *:*
root     ntpd       1603  25 udp6   fe80:2::219:b9ff:fef8:9700:123 *:*
root     ntpd       1603  26 udp6   2001:770:100:81da::1:123 *:*
root     ntpd       1603  27 udp6   ::1:123               *:*
root     ntpd       1603  28 udp6   fe80:8::1:123         *:*
root     ntpd       1603  29 udp4   127.0.0.1:123         *:*
root     ntpd       1603  31 udp6   2001:770:100:1da::2:123 *:*

gif6: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
        tunnel inet XXX.XXX.XXX.XXX --> XXX.XXX.XXX.XXX
        inet6 fe80::20a:faff:fe20:3a1%gif6 prefixlen 64 tentative scopeid 0x9
        inet6 removed --> removed prefixlen 128
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        options=1<ACCEPT_REV_ETHIP_VER>

C.
--
+---------------------------------------------------------------+
Quidquid latine dictum sit, altum sonatur.
MSN: [hidden email]
ICQ: 112562229
GPG: http://www.konundrum.org/schro.asc

attachment0 (851 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Melanie Schulte
In reply to this post by Kevin Oberman-4
Hi,

> What is the address space is the address you are seeing on the interface?
> Is it is a link-local address or one assigned by the router, a static from
> rc.conf or DHCPv6? You should have two inet6 addresses, one is link-local
> (starts with "fe") and another should start with "2". There may be more
> than two.

I fear I cannot answer all of these questions. I don't have any IPv6
addresses configured in rc.conf. Also, I am not using dhcp. Basically
I only have IPv4 networking configured with static addresses --
neither have I actively _disabled_ IPv6.

This is my ifconfig output:

re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
         ether 00:16:36:74:20:76
         inet XXX.XXX.XXX.XXX netmask 0xfffffff0 broadcast XXX.XXX.XXX.XXX
         inet6 fe80::216:36ff:fe74:2076%re0 prefixlen 64 scopeid 0x2
         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
         options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
         inet6 ::1 prefixlen 128
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
         inet 127.0.0.1 netmask 0xff000000
         nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
lo1: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
         options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
         inet 192.168.1.1 netmask 0xffffff00
         inet 192.168.1.2 netmask 0xffffff00
         inet 192.168.1.3 netmask 0xffffff00
         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

Also, I have noticed something: when i disable ntpd_enable in rc.conf
and start ntpd manually after boot up, no such errors are logged. So I
had the impression that is must have something to do with the
timing. I have changed /etc/rc.d/ntpd in such a way that it logs the
output of ifconfig at the beginning. But... there's no difference to
the ifconfig output above. Hence I am not sure what's going on.

Thanks for any help!

~ melanie
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Melanie Schulte
To add a few notes:

I did some more debugging/testing and this behaviour seems to be a bit
random. Sometimes I boot the system and no error is triggered.... the
number of 'cannot assign requested errors' varies between 0 and 2 on
my system and I have no idea what might influence it. :-/

Thanks,
melanie
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Hajimu UMEMOTO
In reply to this post by Melanie Schulte
Hi,

>>>>> On Fri, 15 Mar 2013 22:54:42 +0100 (CET)
>>>>> "M. Schulte" <[hidden email]> said:

m-freebsd> I fear I cannot answer all of these questions. I don't have any IPv6
m-freebsd> addresses configured in rc.conf. Also, I am not using dhcp. Basically
m-freebsd> I only have IPv4 networking configured with static addresses --
m-freebsd> neither have I actively _disabled_ IPv6.

m-freebsd> This is my ifconfig output:

m-freebsd> re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
m-freebsd>         options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
m-freebsd>         ether 00:16:36:74:20:76
m-freebsd>         inet XXX.XXX.XXX.XXX netmask 0xfffffff0 broadcast XXX.XXX.XXX.XXX
m-freebsd>         inet6 fe80::216:36ff:fe74:2076%re0 prefixlen 64 scopeid 0x2
m-freebsd>         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
m-freebsd>         media: Ethernet autoselect (100baseTX <full-duplex>)
m-freebsd>         status: active

It seems IPv6 is disabled by IFDISABLED nd6 option.  Please try the
attached patch to ignore it.

Sincerely,


_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"

ntpd-ifdisabled.diff (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Eggert, Lars
In reply to this post by Schrodinger
Hi,

>> I confirm I have the same issue on 9.1 r247912 , as below:

same here, on FreeBSD 10.0-CURRENT #5 r+16848a4-dirty:

Mar 26 11:43:17  ntpd[2783]: bind() fd 23, family AF_INET6, port 123, scope 1, addr fe80::92e2:baff:fe2b:3a00, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on ix0 (3) for fe80::92e2:baff:fe2b:3a00#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 23, family AF_INET6, port 123, scope 0, addr fd00:cafe:cafe:200::7, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on ix0 (4) for fd00:cafe:cafe:200::7#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 24, family AF_INET6, port 123, scope 2, addr fe80::92e2:baff:fe2b:3a01, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on ix1 (6) for fe80::92e2:baff:fe2b:3a01#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 24, family AF_INET6, port 123, scope 0, addr fd00:cafe:cafe:201::7, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on ix1 (7) for fd00:cafe:cafe:201::7#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 25, family AF_INET6, port 123, scope 3, addr fe80::21b:21ff:fea8:a534, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on em0 (9) for fe80::21b:21ff:fea8:a534#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 25, family AF_INET6, port 123, scope 0, addr fd00:cafe:cafe:100::7, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on em0 (10) for fd00:cafe:cafe:100::7#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 26, family AF_INET6, port 123, scope 4, addr fe80::21b:21ff:fea8:a535, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on em1 (12) for fe80::21b:21ff:fea8:a535#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 26, family AF_INET6, port 123, scope 0, addr fd00:cafe:cafe:101::7, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on em1 (13) for fd00:cafe:cafe:101::7#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 27, family AF_INET6, port 123, scope 5, addr fe80::21b:21ff:fea8:a536, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on em2 (15) for fe80::21b:21ff:fea8:a536#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 27, family AF_INET6, port 123, scope 0, addr fd00:cafe:cafe:102::7, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on em2 (16) for fd00:cafe:cafe:102::7#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 28, family AF_INET6, port 123, scope 6, addr fe80::21b:21ff:fea8:a537, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on em3 (18) for fe80::21b:21ff:fea8:a537#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 28, family AF_INET6, port 123, scope 0, addr fd00:cafe:cafe:103::7, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: unable to create socket on em3 (19) for fd00:cafe:cafe:103::7#123
Mar 26 11:43:17  ntpd[2783]: bind() fd 31, family AF_INET6, port 123, scope 0, addr fd00:cafe:cafe:104::7, mcast=0 flags=0x11 fails: Can't assign requested address
Mar 26 11:43:17  ntpd[2783]: bind() fd 34, family AF_INET6, port 123, scope 0, addr fd00:cafe:cafe:1::7, mcast=0 flags=0x11 fails: Can't assign requested address

>> However, ntpd runs fine and is bound to the following addresses:

same here, running fine.

My ifconfig:

ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO>
        ether 90:e2:ba:2b:3a:00
        inet 10.2.0.7 netmask 0xffffff00 broadcast 10.2.0.255
        inet6 fe80::92e2:baff:fe2b:3a00%ix0 prefixlen 64 scopeid 0x1
        inet6 fd00:cafe:cafe:200::7 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-Twinax <full-duplex>)
        status: active
ix1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=407bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWTSO>
        ether 90:e2:ba:2b:3a:01
        inet 10.2.1.7 netmask 0xffffff00 broadcast 10.2.1.255
        inet6 fe80::92e2:baff:fe2b:3a01%ix1 prefixlen 64 scopeid 0x2
        inet6 fd00:cafe:cafe:201::7 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (10Gbase-Twinax <full-duplex>)
        status: active
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
        ether 00:1b:21:a8:a5:34
        inet 10.1.0.7 netmask 0xffffff00 broadcast 10.1.0.255
        inet6 fe80::21b:21ff:fea8:a534%em0 prefixlen 64 scopeid 0x3
        inet6 fd00:cafe:cafe:100::7 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
        ether 00:1b:21:a8:a5:35
        inet 10.1.1.7 netmask 0xffffff00 broadcast 10.1.1.255
        inet6 fe80::21b:21ff:fea8:a535%em1 prefixlen 64 scopeid 0x4
        inet6 fd00:cafe:cafe:101::7 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
em2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
        ether 00:1b:21:a8:a5:36
        inet 10.1.2.7 netmask 0xffffff00 broadcast 10.1.2.255
        inet6 fe80::21b:21ff:fea8:a536%em2 prefixlen 64 scopeid 0x5
        inet6 fd00:cafe:cafe:102::7 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: no carrier
em3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
        ether 00:1b:21:a8:a5:37
        inet 10.1.3.7 netmask 0xffffff00 broadcast 10.1.3.255
        inet6 fe80::21b:21ff:fea8:a537%em3 prefixlen 64 scopeid 0x6
        inet6 fd00:cafe:cafe:103::7 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: no carrier
em4: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
        ether 00:a0:98:30:c2:28
        inet6 fe80::2a0:98ff:fe30:c228%em4 prefixlen 64 scopeid 0x7
        inet 10.11.12.7 netmask 0xffffff00 broadcast 10.11.12.255
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
em5: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
        ether 00:a0:98:30:c2:29
        inet 10.1.4.7 netmask 0xffffff00 broadcast 10.1.4.255
        inet6 fe80::2a0:98ff:fe30:c229%em5 prefixlen 64 scopeid 0x8
        inet6 fd00:cafe:cafe:104::7 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
        ether 00:a0:98:30:c2:2c
        inet 10.0.0.7 netmask 0xffffff00 broadcast 10.0.0.255
        inet6 fe80::2a0:98ff:fe30:c22c%bge0 prefixlen 64 scopeid 0x9
        inet6 fd00:cafe:cafe::7 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
bge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
        ether 00:a0:98:30:c2:2d
        inet 10.0.1.7 netmask 0xffffff00 broadcast 10.0.1.255
        inet6 fe80::2a0:98ff:fe30:c22d%bge1 prefixlen 64 scopeid 0xa
        inet6 fd00:cafe:cafe:1::7 prefixlen 64
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0xb
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

Lars

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Kit Sin-2
In reply to this post by Melanie Schulte
How do you configure your network interfaces? Using /etc/start_if* or /etc/rc.conf?<br/>
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Eggert, Lars
On Mar 26, 2013, at 12:59, <[hidden email]>
 wrote:
> How do you configure your network interfaces? Using /etc/start_if* or /etc/rc.conf?<br/>

The latter.

(Actually, most of them are configured in rc.local with a bit of shell code that generates the IP address from the MAC address for a set of machines.)

Lars
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Kit Sin-2
--- On Tue, 3/26/13, Eggert, Lars <[hidden email]> wrote:

> On Mar 26, 2013, at 12:59, <[hidden email]>
>  wrote:
> > How do you configure your network interfaces? Using
> /etc/start_if* or /etc/rc.conf?<br/>
>
> The latter.
>
> (Actually, most of them are configured in rc.local with a
> bit of shell code that generates the IP address from the MAC
> address for a set of machines.)
>
> Lars

i had seen the same error messages while trying to configure wlan0 using start_if.wlan0.

i think that when an interface is first created, the flag ifdisabled is set by default. my guess is there exists a small window of time when the interface is up, ipv6 is configured but marked ifdisabled, and if ntpd happens to start during this period of time, you will see the failure messages.

you may want to check your shell code again and perhaps the rc scripts too and see how they interact.

kit

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Kit Sin-2
--- On Tue, 3/26/13, kit <[hidden email]> wrote:

> --- On Tue, 3/26/13, Eggert, Lars
> <[hidden email]>
> wrote:
> > On Mar 26, 2013, at 12:59, <[hidden email]>
> >  wrote:
> > > How do you configure your network interfaces?
> Using
> > /etc/start_if* or /etc/rc.conf?<br/>
> >
> > The latter.
> >
> > (Actually, most of them are configured in rc.local with
> a
> > bit of shell code that generates the IP address from
> the MAC
> > address for a set of machines.)
> >
> > Lars
>
> i had seen the same error messages while trying to configure
> wlan0 using start_if.wlan0.
>
> i think that when an interface is first created, the flag
> ifdisabled is set by default. my guess is there exists a
> small window of time when the interface is up, ipv6 is
> configured but marked ifdisabled, and if ntpd happens to
> start during this period of time, you will see the failure
> messages.
>
> you may want to check your shell code again and perhaps the
> rc scripts too and see how they interact.
>
> kit

try setting ipv6_activate_all_interfaces to yes and configuring the corresponding $ifconfig_IF_ipv6 in your rc.conf if you haven't done so already, and see if they help.

from /etc/defaults/rc.conf:

ipv6_activate_all_interfaces="NO"       # If NO, interfaces which have no
                                        # corresponding $ifconfig_IF_ipv6 is
                                        # marked as IFDISABLED for security
                                        # reason.

kit
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Eggert, Lars
Hi,

On Mar 26, 2013, at 15:39, kit <[hidden email]> wrote:
>
> try setting ipv6_activate_all_interfaces to yes

I had that set all along.

> and configuring the corresponding $ifconfig_IF_ipv6 in your rc.conf if you haven't done so already

Can't really do this, because dhclient needs to have finished so I can generate IPv6 addresses based on the IPv4 address & MAC address of the interfaces. (Yes, this is an ugly hack, but these are lab machines.)

Lars
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

hiren panchasara
I see this message on july 2014 time-frame -CURRENT. I tried to
disable IPv6 in rc.conf via ipv6_activate_all_interfaces="NO" without
success.

Has this been fixed? Or any workarounds?
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

Hajimu UMEMOTO
Hi,

>>>>> On Wed, 7 Jan 2015 16:56:58 -0800
>>>>> hiren panchasara <[hidden email]> said:

hiren> I see this message on july 2014 time-frame -CURRENT. I tried to
hiren> disable IPv6 in rc.conf via ipv6_activate_all_interfaces="NO" without
hiren> success.

hiren> Has this been fixed? Or any workarounds?

Perhaps, your interface has an IPv6 link-local address which is
tentative state.
Please try the attached patch.  This patch ignores a tentative
address.

Sincerely,



--
Hajimu UMEMOTO
[hidden email]  ume@{,jp.}FreeBSD.org
http://www.mahoroba.org/~ume/

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"

ntp_io.c-tentative.diff (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

hiren panchasara
On Thu, Jan 8, 2015 at 9:28 AM, Hajimu UMEMOTO <[hidden email]> wrote:

> Hi,
>
>>>>>> On Wed, 7 Jan 2015 16:56:58 -0800
>>>>>> hiren panchasara <[hidden email]> said:
>
> hiren> I see this message on july 2014 time-frame -CURRENT. I tried to
> hiren> disable IPv6 in rc.conf via ipv6_activate_all_interfaces="NO" without
> hiren> success.
>
> hiren> Has this been fixed? Or any workarounds?
>
> Perhaps, your interface has an IPv6 link-local address which is
> tentative state.
> Please try the attached patch.  This patch ignores a tentative
> address.

Indeed its in tentative state and I figured it was causing the issue.
Getting it out of tentative state (by enabling IPv6 by 'inet6
-ifdisabled' "fixed" the problem.)
But your patch seems like a right way to do it. I'll try it out and report back.

Btw, do you mind opening a phabricator review request so we can get a
closure on this?

cheers,
Hiren
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

hiren panchasara
On Thu, Jan 8, 2015 at 9:48 AM, hiren panchasara
<[hidden email]> wrote:

> On Thu, Jan 8, 2015 at 9:28 AM, Hajimu UMEMOTO <[hidden email]> wrote:
>> Hi,
>>
>>>>>>> On Wed, 7 Jan 2015 16:56:58 -0800
>>>>>>> hiren panchasara <[hidden email]> said:
>>
>> hiren> I see this message on july 2014 time-frame -CURRENT. I tried to
>> hiren> disable IPv6 in rc.conf via ipv6_activate_all_interfaces="NO" without
>> hiren> success.
>>
>> hiren> Has this been fixed? Or any workarounds?
>>
>> Perhaps, your interface has an IPv6 link-local address which is
>> tentative state.
>> Please try the attached patch.  This patch ignores a tentative
>> address.
>
> Indeed its in tentative state and I figured it was causing the issue.
> Getting it out of tentative state (by enabling IPv6 by 'inet6
> -ifdisabled' "fixed" the problem.)
> But your patch seems like a right way to do it. I'll try it out and report back.
>

Attached patch is fixing the problem for me.

cheers,
Hiren

> Btw, do you mind opening a phabricator review request so we can get a
> closure on this?
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: ntpd bind() failure: Can't assign requested address

hiren panchasara
In reply to this post by hiren panchasara
On Thu, Jan 8, 2015 at 9:48 AM, hiren panchasara
<[hidden email]> wrote:
[skip]
> Btw, do you mind opening a phabricator review request so we can get a
> closure on this?

Thanks for the patch ume@. I've committed it to -head and will mfc in a week.

https://reviews.freebsd.org/D1527
https://svnweb.freebsd.org/base?view=revision&revision=277202

Cheers,
Hiren
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[hidden email]"