Rob Janssen wrote:
I've found a list at http://eng.hexago.com/services/ntp.shtml. All
except time.ncore.pl seem to work.
Do you get good latency on ipv6 servers? I get the impression that a
lot of ipv6 routing is going via encapsulation tunnels and so it is
probably less optimal than ipv4.
For the servers from the list from my server (native connectivity, no
tunnel overhead). This is the delay reported by ntpdate -d -u <server>:
IPv6 IPv4
ntp.hexago.com: 0.14337 dead
ntp.rhrk.uni-kl.de: 0.03886 0.03922
ntp6.remco.org: 0.14565 n/a
chime3.ipv6.surfnet.nl: 0.05003 0.04413
ntp6.space.net: 0.02893 0.02847
ntp.ipv6.linux.ee: dead n/a
noc.sixxs.net: 0.04922 0.04185
nlams01.sixxs.net: 0.05014 0.04199
nlams02.sixxs.net: NXDOMAIN
ntp1.bit.nl: 0.04121 0.04279
ntp2.bit.nl: 0.04172 0.04247
ntp.doubleukay.com: 0.38478 0.37715
time.ncore.pl: n/a dead
I used chime3.surfnet.nl for the IPv4 address of chime3.ipv6.surfnet.nl.
As you can see IPv6 is max. 10ms worse than IPv4 (nlams01 and
noc.sixxs.net are at the same provider), with same or even slightly
better latency at some occasions.
Bad latency is a FUD nowadays if you choose your providers carefully (I
admit that this is not always possible in some regions).
Regards,
Bernhard
--
Bernhard Schmidt Netzplanung / IPv6
Leibniz-Rechenzentrum der Bayerischen Akademie der Wissenschaften
Boltzmannstr. 1 D-85748 Garching bei Muenchen
Tel: +49 89 35831-7885 [EMAIL PROTECTED]
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
