On Thu, 01 Feb 2007 18:33:33 +0300
Denis Lagno <dlagno@rambler.ru> wrote:

> Christian Biere wrote:
> > Have you checked your ntp.conf? It seems one of the listed hosts
> > resolves to an IPv6 address but you have no non-local IPv6
> > connectivity.
> yes, it is right:
> ntp.via.ecp.fr is an alias for krishna.via.ecp.fr.
> krishna.via.ecp.fr has address 138.195.130.71
> krishna.via.ecp.fr has IPv6 address
> 2002:8ac3:802d:1243:204:e2ff:fe10:5c44 It is just confusing that
> those messages appear in ntpd logs only when ntpd is started _before_
> dhclient sets interface ex0, and pppd establishes ppp0.  If I start
> or restart ntpd after ex0 and ppp0 are established, then those error
> messages do not appear.  This ipv6 address is unaccessible in any
> case.

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
Jan 22 09:40:01 berkshire ntpd[21195]: kernel time sync status 2040
Jan 22 09:40:01 berkshire ntpd[21195]: frequency initialized -234.733 PPM from /var/db/ntp.drift
Jan 22 09:40:11 berkshire ntpd[21195]: Listening on interface #8 ppp0, fe80::211:25ff:fe43:e8a4#123 Enabled
Jan 22 09:49:54 berkshire ntpd[21195]: time reset +0.878150 s
Jan 22 09:49:54 berkshire ntpd[21195]: kernel time sync status change 6001
Jan 22 09:56:20 berkshire ntpd[21195]: kernel time sync status change 2001
Jan 22 09:56:55 berkshire ntpd[21195]: Deleting interface #6 ppp0, 70.198.25.255#123, interface stats: received=31, sent=50, dropped=0, active_time=1004 secs
Jan 22 09:56:55 berkshire ntpd[21195]: Deleting interface #8 ppp0, fe80::211:25ff:fe43:e8a4#123, interface stats: received=0, sent=0, dropped=0, active_time=1003 secs
Jan 22 09:57:08 berkshire ntpd[21195]: ntpd exiting on signal 15



		--Steve Bellovin, http://www.cs.columbia.edu/~smb