unruh wrote: > On 2010-10-24, Richard B. Gilbert <[email protected]> wrote: >> On 10/22/2010 2:24 PM, Florin Andrei wrote: >>> server 127.127.1.0 # local clock >>> fudge 127.127.1.0 stratum 10 >>> driftfile /etc/ntp/drift >>> restrict 127.0.0.0 mask 255.0.0.0 >>> restrict 192.168.3.0 mask 255.255.255.0 nomodify notrap >>> restrict default ignore >> >> Lose the restrict statements. Getting it working first!
I absolutely agree. >> You may have to ask your networking people to allow NTP traffic to get >> through the firewall. Port 123 should be allowed. > > He says ntpdate works. Yes, but a firewall may be a problem anyway: - If you run "ntpdate -q server" then ntpdate uses an unprivileged port. - If you run "ntpdate server" then ntpdate uses port 123 Please note whereas the former command (query only) can be used any time, the latter works *only* while ntpd is *not* running. On the other hand only the latter ntpdate command is affected by the same firewall rules as ntpd. Martin -- Martin Burnicki Meinberg Funkuhren Bad Pyrmont Germany _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
