This one's amusing (well, it depends) - I've been playing with ntp multicast on ipv6 for a while. It works very well (on ff05::101), but today I noticed a tiny difference: An ntp client (A) that uses the ipv6 multicast: # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== *fe80::202:a5ff: 192.168.2.254 2 m 12 16 376 -0.388 -23.481 2.378 An ntp client (B) that is configured as ipv4 broadcastclient: # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== *192.168.2.137 .DCFa. 1 u 13 16 376 0.266 0.026 0.283 The time server (192.168.2.137,192.168.2.254) has a DCF77 receiver, and is stratum 1. Notice the _refid_. The question is - why does (B) see the time server as stratum 1, when (A) sees it as stratum 2? Here it is quite clear, the ipv4 connection is preferred over the ipv6 multicast: # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== *192.168.2.254 .DCFa. 1 u 245 256 377 0.378 6.466 1.371 xfe80::202:a5ff: 192.168.2.254 2 m 4 16 377 0.288 117.385 0.458 I know this would be better asked on the ntp list, but still :-) -- Per Jessen, Zürich (6.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org