Hi,

the bind failure has been reported as bug #771 in the NTP project.

Frank

Steven M. Bellovin wrote:

>On Thu, 01 Feb 2007 18:33:33 +0300
>Denis Lagno <dlagno@rambler.ru> wrote:
>
>  
>
>>Christian Biere wrote:
>>    
>>
>>>...
>>>
>>>      
>>>
>Here are some v6-related messages when I fire up ntpd after bringing
>up a ppp link:
>
>Jan 22 09:40:01 berkshire ntpd[21195]: precision = 4.190 usec
>Jan 22 09:40:01 berkshire ntpd[21195]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
>Jan 22 09:40:01 berkshire ntpd[21195]: Listening on interface #1 wildcard, ::#123 Disabled
>Jan 22 09:40:01 berkshire ntpd[21195]: Listening on interface #2 wm0, fe80::211:25ff:fe43:e8a4#123 Enabled
>Jan 22 09:40:01 berkshire ntpd[21195]: Listening on interface #3 lo0, 127.0.0.1#123 Enabled
>Jan 22 09:40:01 berkshire ntpd[21195]: Listening on interface #4 lo0, ::1#123 Enabled
>Jan 22 09:40:01 berkshire ntpd[21195]: Listening on interface #5 lo0, fe80::1#123 Enabled
>Jan 22 09:40:01 berkshire ntpd[21195]: Listening on interface #6 ppp0, 70.198.25.255#123 Enabled
>Jan 22 09:40:01 berkshire ntpd[21195]: bind() fd 27, family 24, port 123, scope 5, addr fe80::211:25ff:fe43:e8a4, in6_is_addr_multicast=0 flags=19 fails: Can't assign requested address
>Jan 22 09:40:01 berkshire ntpd[21195]: unable to create socket on ppp0 (7) for fe80::211:25ff:fe43:e8a4#123
>Jan 22 09:40:01 berkshire ntpd[21195]: failed to initialize interface for address fe80::211:25ff:fe43:e8a4
>Jan 22 09:40:01 berkshire ntpd[21195]: Listening on routing socket on fd #27 for interface updates
>  
>