On Sat, 2006-04-15 at 12:48 -0400, Guillaume Filion wrote:
> So please query 0.ntp-pool-test.logidac.com,
> 1.ntp-pool-test.logidac.com, etc and see what NTP server you are
> getting.
Here's what I got, in order from 0.ntp-pool-test.logidac.com through
4.ntp-pool-test.logidac.com.
Ping Time
==============
0. 66.228.198.10 1 ms 1 hop (That's me, in Shoreline, WA, USA)
1. 66.250.45.2 125 ms 14 hops (Washington, DC, USA)
2. 38.112.70.6 117 ms 16 hops (Washington, DC, USA)
3. 192.83.249.31 55 ms 11 hops (Emeryville, CA, USA)
4. 62.206.253.10 250 ms 21 hops (Germany)
(I would call the myself and the Emeryville server both nearby, and good
candidates for use as a pool server. The Washington, DC servers are on
the other side of the continent --- there have to be closer servers in
the pool. The German server --- that's on the other side of the
globe :-/. So two of the five are good picks, one is a terrible pick,
and two are mediocre.)
>From the 12 IPs I currently get for us.pool.ntp.org (which includes
192.83.249.31, listed above) there are three other hosts with better
ping times than the three worst results above.
209.204.157.98 65 ms 11 hops (Santa Rosa, CA, USA)
209.204.159.18 62 ms 12 hops (Santa Rosa, CA, USA)
209.223.236.234 91 ms 14 hops (Dallas, TX, USA)
(Locations determined using http://www.rleeden.no-ip.com/geotool.php )
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
