On Mon, Mar 14, 2016 at 10:12 AM, Per Jessen <per@computer.org> wrote:
Andrei Borzenkov wrote:
13.03.2016 21:35, Per Jessen пишет:
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?
What "it" you mean? A sees stratum 2 server fe80::202:a5ff: which itself has as reference clock stratum 1 server. What exactly is wrong here? Your question sounds like "it" is the same server, but you gave no evidence that fe80::202:a5ff: is the same as 192.168.2.137.
Sorry, yes, _it_ is the same server.
How do you know it? ntpq -np displays truncated IPv6 address, so you do not even see what server is used. See http://bugs.ntp.org/show_bug.cgi?id=1128 how to show verify full peer address. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org