On 20-10-09 16:40, Kiss Gábor wrote:
>>> You can easily convince me of this if you present a screenshot. :-)
>
> Have you noticed, that 216.14.97.75 is unreachable? :-)
> Please have look on value "0" in "reach" column.
My current situation: st.1 with full reach, low jitter (better than the
current peer), even fairly low delay (given it is abroad), but the largest
offset.
remote refid st t when poll reach delay offset jitter
=======================================================================
+auth1.xs4all.nl 193.79.237.14 2 u 630 1024 377 7.517 -0.189 0.050
*doei.cs.uu.nl 131.211.80.22 2 u 912 1024 377 9.872 -0.190 0.185
-arethusa.tweake 193.190.230.66 2 u 500 1024 377 8.142 1.344 0.388
-204.9.53.11 128.9.176.30 2 u 654 1024 377 9.241 -1.478 0.096
-pruts.nl 193.79.237.14 2 u 1009 1024 377 7.544 -0.324 0.163
-ntp2.hro.nl 193.79.237.14 2 u 657 1024 377 13.369 1.811 0.176
-tick.ntp.comput 213.10.47.241 2 u 647 1024 377 8.957 -0.510 0.236
-ntp2.rrze.uni-e .PPS. 1 u 891 1024 377 27.969 -5.226 0.129
-tom.quae.co.uk 130.88.212.143 3 u 942 1024 377 17.503 1.323 0.505
-ntp1.winlin.be 193.190.230.65 2 u 933 1024 377 14.681 -0.010 0.224
+proteus.technov 192.36.144.22 2 u 891 1024 377 19.471 -0.111 0.557
-ns1.vaksdalnet. 192.36.133.17 2 u 879 1024 377 41.307 -2.752 0.324
LOCAL(0) .LOCL. 10 l 59 64 377 0.000 0.000 0.001
Convinced? ;-)
Arnold
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
