On Wed, Sep 22, 2004 at 08:31:12PM -0400, Gene Heskett wrote:[ Various Verizon-related conversation deleted. ]
Starting locally on the primary traceroute list, I finally hit one on the 17th hop but its a: stratum 16, offset 0.062642, root distance 0.006480
Not a problem ... if you traceroute to other 'interesting' places you will get a different list of routers. With a bit of attention you can discover what is close to you.
We've got a T1 from one of Verizon's competitors - Cavalier Telephone. All three of their routers upstream from me provided NTP service.
remote refid st t when poll reach delay offset jitter ============================================================================== -64.83.60.101.ds 192.5.41.40 2 u 94 128 377 4.681 -91.131 16.643 xatm0-1-0-401-ds 192.5.41.40 2 u 99 128 377 13.307 4.671 48.380 +pos0-2-oc3.core 192.5.41.40 2 u 103 128 377 13.582 -85.782 30.839
The delay from Cavtel's NTP servers was an order of magnitude in lower delay than than clock.redhat.com and the closest cavtel server has one-twentieth of the delay of getting to washington.edu for me.
I'm not sure if its real or not, but it certainly seemed I was syncing time faster after adding these to my config.
-- </chris>
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
-- C.A.R. Hoare
