[ntp:questions] Why does ntp keep changing my conf file?

Steve Kostecke kostecke at ntp.org
Thu Sep 16 21:20:47 UTC 2010


On 2010-09-16, Daniel Havey <dhavey at yahoo.com> wrote:
>
> But it doesn't work properly either ;^(
> First of all this looks fishy:
> [dhavey at node0 /etc]$ ntpq -p
>      remote      refid   st t when poll reach  delay  offset  jitter
>=====================================================================
>  cogsworth.aero. .INIT.  16 u    - 1024    0   0.000   0.000   0.000
>  dns.aero.org    .INIT.  16 u    - 1024    0   0.000   0.000   0.000
>
> Those delay, offset, and jitter values are too good to be true

That peer status billboard shows that this ntpd has not been able to
poll the remote time servers.

> and the other machine won't connect: [dhavey at node1 ~]$ sudo ntpdate
> node0.rms01.wgs.sntb.aero.org 16 Sep 10:24:03 ntpdate[25389]: no
> server suitable for synchronization found

[snip]

> [dhavey at node0 ~/MANET]$ more /etc/ntp.conf
> restrict default noserve nomodify
> restrict -6 default noserve nomodify

noserve blocks all NTP time service packets both incoming and
outgoing. This means that the default posture of this ntpd is to be
_neither_ a client nor a server.

> restrict 127.0.0.1
> restrict -6 ::1
> restrict 192.168.0.0 mask 255.255.252.0 notrust nomodify notrap

notrust means to ignore all NTP packets unless they are
cryptographically authenticated.

> restrict 130.221.24.100 mask 255.255.255.255 nomodify notrap noquery
> server 130.221.24.100
> restrict 130.221.128.2 mask 255.255.255.255 nomodify notrap noquery
> server 130.221.128.2
> driftfile /var/lib/ntp/drift
> broadcastdelay  0.008

The broadcast delay line does nothing in your case.

Please comment out your restrict lines and restart ntpd. If that does
not work something is blocking 123/UDP.

-- 
Steve Kostecke <kostecke at ntp.org>
NTP Public Services Project - http://support.ntp.org/




More information about the questions mailing list