Hello all,
let me try to explain my thoughts.
~ host heise.de
heise.de has address 193.99.144.80
heise.de has IPv6 address 2a02:2e0:3fe:100::8
heise.de mail is handled by 10 relay.heise.de.
~ host pool.ntp.org
pool.ntp.org has address 129.70.132.33
pool.ntp.org has address 85.214.71.202
pool.ntp.org has address 83.169.19.197
You may see that IPv6 is working on my system, but there is no IPv6 system in
the pool and that's the reason why I decided to join pool.ntp.org.
~ ping6 -c 2 www.pool.ntp.org
PING www.pool.ntp.org(2607:f238:2::51) 56 data bytes
64 bytes from 2607:f238:2::51: icmp_seq=1 ttl=48 time=214 ms
64 bytes from 2607:f238:2::51: icmp_seq=2 ttl=48 time=215 ms
--- www.pool.ntp.org ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1007ms
rtt min/avg/max/mdev = 214.739/215.123/215.507/0.384 ms
~ ping -c 2 www.pool.ntp.org
PING ntppool-varnish.develooper.com (207.171.3.6) 56(84) bytes of data.
64 bytes from netblk-207-171-3-6.phyber.com (207.171.3.6): icmp_seq=1 ttl=57
time=193 ms
64 bytes from netblk-207-171-3-6.phyber.com (207.171.3.6): icmp_seq=2 ttl=57
time=200 ms
--- ntppool-varnish.develooper.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1010ms
rtt min/avg/max/mdev = 193.516/197.029/200.543/3.541 ms
~ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
+ptbtime3.ptb.de .PTB. 1 u 76 1024 377 44.672 4.776 0.176
+time.nist.gov .ACTS. 1 u 453 1024 337 198.557 1.567 9.639
*zaphod 192.53.103.108 2 u 131 1024 377 1.783 2.757 0.596
-alix02 192.168.1.2 3 u 65 128 377 127.818 3.807 7.072
LOCAL(0) .LOCL. 6 l 47 64 377 0.000 0.000 0.002
As one can see my system is in sync with some other ntp servers. IPv6 is
working, the IP is statically assigned to me. There is a little delay in the
rtt when pinging other IPv6 enabled hosts, but I think we all know that ntp
handles this delay and will adjust the time accordingly. Pinging IPv4 hosts is
a bit faster.
My system gets a score from -9,8 (¹) and therefore will not enter the pool. I
think this is because of the large paket rtt ... and when I do a "host
pool.ntp.org" I do not see any other IPv6 enabled ntp timekeepers. I assume
they all may have the same problem as I do, I mean: they all may have a 200 ms
or so rtt and the measurement logic counts this as offset from the time.
So I kindly ask to do some modifications for getting IPv6 ntp servers in the
pool, e.g. setting the the allowed offset higher than normal to get some IPv6
servers in the pool. Or at least think about it ... for a limited time or for
testing.
Thank you.
--
Stephan
¹)
http://www.pool.ntp.org/scores/2001:6f8:900:7a6::2
--
GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit
gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
