On Mon, 30 Jul 2007, John Ackermann N8UR wrote:
Ask Bjørn Hansen wrote:
On Jul 29, 2007, at 9:57, Ames, Stephen wrote:
meow.febo.com is returning from 192.168.1.234 instead of a public
IP for the us.pool.ntp.org. Is there any way to exclude that server?
Happened already:
http://www.pool.ntp.org/scores/24.123.66.139
I run meow.febo.com. Not sure what's happening other than that we had a
network outage overnight; the network is back up as of about 0915 EDT.
The 192.168.1.234 address is used here for an internal NTP server
(tock.febo.com) but that should be visible only on my internal network.
I have no idea how it would have propagated outside.
John
You seem to be right, everything is fine viewed from here !
It is OK to have time source on your internal network (of course ;-) as
long as you can be reached from the outside, which is the case for your
server.
So I am not sure what the first poster meant either...
It seems to me that you have no action to take,
ntpq -p meow.febo.com
remote refid st t when poll reach delay offset
jitter
==============================================================================
+192.168.1.233 .LOR. 1 u 28 64 377 1.263 -0.078
0.027
*192.168.1.234 .GPSZ. 1 u 22 64 377 1.448 -0.104
0.085
+192.168.1.235 .WWVB. 1 u 28 64 377 1.311 -0.196
0.057
192.168.1.229 .STEP. 16 u - 64 0 0.000 0.000
0.000
192.168.1.224 192.168.1.234 2 u 22 64 377 0.583 0.159
1.187
-time-B.timefreq .ACTS. 1 u 47 64 377 50.691 5.974
4.867
-tock.usno.navy. .USNO. 1 u 41 64 377 36.908 -0.498
7.546
[EMAIL PROTECTED]:/home/hbenoit/java17/joomla/templates/rhuk_milkyway#
Louis
http://www.oc9.com
http://www.pool.ntp.org/scores/207.236.226.149
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
