[ntp:questions] Interface restrictions confusing me
Juergen Beisert
juergen at kreuzholzen.de
Sun Oct 11 15:15:41 UTC 2009
Hi list,
also the access restrictions confusing me. In my local net one host provides a
DCF77 based clock reference via ntp.
Two other hosts should use this service, but itself not acting as a timer
server. So, I added the 'restrict default noserve' line to _their_ (=client
side) '/etc/ntp.conf'. After that, they are stopping using my time server.
On my time server:
me at time_server$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
LOCAL(0) .LOCL. 10 l 22 64 377 0.000 0.000 0.004
*SHM(0) .SHM. 9 l 12 64 377 0.000 0.681 0.963
Here, when the clients are running without the 'restrict default noserve'
setting:
me at client$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*time_server SHM(0) 10 u 41 64 377 0.493 30.398 6.463
LOCAL(0) .LOCL. 10 l 27 64 377 0.000 0.000 0.004
Here, with the 'restrict default noserve' setting:
me at client$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
time_server .INIT. 16 - - 1024 0 0.000 0.000 0.000
*LOCAL(0) .LOCL. 10 l 8 64 377 0.000 0.000 0.008
When running 'tftpdump' on my time server I can see, the client is still
sending queries to the time server, independent from the setting. Why a local
ntp stops syncing to another network time server, when itself should not act
as a server?
Maybe I should read the configuration documentation again. Can someone point
me to the part I should read more carefully?
Regards,
Juergen
More information about the questions
mailing list