Hi, I'm aware that there were some troubles with IPv6 in Germany. Does it explain the following error message?
I tried to add a new IPv6 NTP server to the pool. First, the geolocation didn't work, so I manually chose "Germany" as the server location. After clicking on "Yes, add it" the following message appears: Invalid stratum response from 2a02:a00:1009:6202::123 (Your server is in stratum ). Is your server configured properly? Is public access allowed? If you just restarted your ntpd, then it might still be stabilizing the timesources - try again in 10-20 minutes. The NTP service is running for over an hour now and could be added with it's IPv4 address without problems. Additionally, with tcpdump I can see the server answering correctly (in my opinion): --- REQUEST TO THE SERVER --- 2607:f238:2::17.39342 > 2a02:a00:1009:6202::123.123: [udp sum ok] NTPv3, length 48 Client, Leap indicator: (0), Stratum 0 (unspecified), poll 0s, precision 0 Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec) Reference Timestamp: 0.000000000 Originator Timestamp: 0.000000000 Receive Timestamp: 0.000000000 Transmit Timestamp: 1373059605.767578125 (2079/08/12 05:55:01) Originator - Receive Timestamp: 0.000000000 Originator - Transmit Timestamp: 1373059605.767578125 (2079/08/12 05:55:01) --- ANSWER FROM MY SERVER --- 23:26:33.372459 IP6 (hlim 64, next-header UDP (17) payload length: 56) 2a02:a00:1009:6202::123.123 > 2607:f238:2::17.39342: [udp sum ok] NTPv3, length 48 Server, Leap indicator: (0), Stratum 2 (secondary reference), poll 0s, precision -20 Root Delay: 0.019165, Root dispersion: 0.014160, Reference-ID: 192.53.103.103 Reference Timestamp: 3582048326.165654972 (2013/07/05 23:25:26) Originator Timestamp: 1373059605.767578125 (2079/08/12 05:55:01) Receive Timestamp: 3582048405.230885639 (2013/07/05 23:26:45) Transmit Timestamp: 3582048405.230953708 (2013/07/05 23:26:45) Originator - Receive Timestamp: -2085978496.536692500 Originator - Transmit Timestamp: -2085978496.536624431 Especially, the stratum flag seems to be ok? Is there anything I can do about it? Or might this be a bug resulting from the firmware bug at HE? Thanks in advance and greetings from Wuppertal, Germany Max Grobecker _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
