On 12/27/2009 02:55 PM, Matt Nordhoff wrote: > 27 Dec 13:48:36 ntpdate[3254]: adjust time server 80.101.128.228 offset > 0.034292 sec > > Seems good, though the clock is a couple ms off. (Only about 2.4 from > two other machines, one of them only ~15 ms away, though.) > > It's very nice that latency is about the same over both IPv4 and IPv6. > > (Those tests were from tick.mattnordhoff.com, which uses an HE tunnel, > FWIW.) > >> If IPv6 works well enough: how to make this known to the pool? > > Just add the IP, same as anything else. (Last I tried, adding a hostname > didn't work; apparently it doesn't look up AAAA records.) > > Currently, the pool doesn't actually support IPv6 NTP servers, so, > though you can add it, it won't be distributed, and the monitoring and > statistics won't work either.
I restarted ntpd a few times to get stuff working. ntpd deleted the sit1 ipv6 interface. So I use 'ntpd -U 0' to stop that. Any better methods? Thanks for testing. Things appear to work now. I can see you on the `ntpdc -c monlist` output. Any timeframe for ipv6 support in the pool? Udo _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
