Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Mar 2013 14:38:12 +0100
From:      Fleuriot Damien <ml@my.gd>
To:        "M. Schulte" <m-freebsd@fuglos.org>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   Re: ntpd bind() failure: Can't assign requested address
Message-ID:  <EB512A35-E253-4C00-8293-029DAEBD345B@my.gd>
In-Reply-To: <76E2EE0D-B6D3-428E-9112-AF0E04E98DDE@my.gd>
References:  <alpine.BSF.2.00.1303122241080.77297@m.fuglos.org> <76E2EE0D-B6D3-428E-9112-AF0E04E98DDE@my.gd>

next in thread | previous in thread | raw e-mail | index | archive | help

On Mar 12, 2013, at 11:44 PM, Damien Fleuriot <ml@my.gd> wrote:

>=20
> On 12 Mar 2013, at 22:42, "M. Schulte" <m-freebsd@fuglos.org> wrote:
>=20
>> Hi!
>>=20
>> [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.]
>>=20
>> 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:
>>=20
>>  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=3D0 flags=3D0x11 fails: Can't assign =
requested address
>>  ntpd[767]: unable to create socket on re0 (3) for =
fe80::216:36ff:fe74:2076#123
>>=20
>> 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.
>>=20
>> Although I could find some threads where people were discussing the
>> same problem, none of the mentioned suggestions fixed this for me.
>>=20
>> In particular I tried setting
>>=20
>>  ipv6_activate_all_interfaces=3D"YES"
>>=20
>> in rc.conf -- didn't fix the problem.
>>=20
>> 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.
>>=20
>> Would be great if somebody could give me a hint into the right
>> direction. Anybody else experiencing this? Thank you very much!
>>=20
>> ~ melanie
>>=20
>=20
> I'll check tomorrow if we have the same issue at work, although it =
doesn't look familiar.
>=20
> 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=3D0 flags=3D0x11 =
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    *:*




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EB512A35-E253-4C00-8293-029DAEBD345B>