how to sync time for LAN (ntp)?
in [Slackware]
|
Prev: idebus=66 not recognized on current.
Next: Msmtp (was: Re: able to retrieve but not send email with elm, nail, and mutt)
From: B.Yanchitsky on 1 Feb 2008 13:01 I've regulary used funny "timed" BSD daemon to do that, but now for some reasons this is impossible. What I have to do: I have 2 computers with 2 local IP 192.168.0.30 and 192.168.0.70 (netmask 255.255.255.0). The first one (.30), I would like to act as a source of time (using its internal clock) for the second (.70). Nothing more. I've straggled for 4-5 hours, googled around everything about ntpd and ntpdate and completely failed. What should be in ntp.conf on the server side and on the client side? Security issues are not import for me. timed BSD daemon does not have any configuration files, what a great program. --- Bogdan
From: Petri Kaukasoina on 1 Feb 2008 13:08 <B.Yanchitsky(a)gmail.com> wrote: >What I have to do: I have 2 >computers with 2 local IP >192.168.0.30 and 192.168.0.70 (netmask 255.255.255.0). >The first one (.30), I would like to act as a source of time (using >its internal clock) for the second (.70). Nothing more. I've straggled >for 4-5 hours, googled around everything about ntpd and ntpdate and >completely failed. What should be in ntp.conf on the server side and >on the client side? Security issues are not import for me. Server 192.168.0.30 ntp.conf: server 127.127.1.0 fudge 127.127.1.0 stratum 11 Client 192.168.0.70 ntp.conf: server 192.168.0.30 iburst driftfile /etc/ntp/drift
From: B.Yanchitsky on 1 Feb 2008 13:19 On Feb 1, 8:08 pm, kaukasoina708n8s6l...(a)sci.fi (Petri Kaukasoina) wrote: > > Server 192.168.0.30 ntp.conf: > > server 127.127.1.0 > fudge 127.127.1.0 stratum 11 > > Client 192.168.0.70 ntp.conf: > > server 192.168.0.30 iburst > driftfile /etc/ntp/drift Thanks, but does not work. I put server 127.127.1.0# fudge 127.127.1.0 stratum 11 into ntp.conf on the server side, and the command ntpdate -b 192.168.0.30 on the client side produces the following 11 Jan 02:00:39 ntpdate[22803]: no server suitable for synchronization found --- Bogdan
From: B.Yanchitsky on 1 Feb 2008 13:36 On Feb 1, 8:08 pm, kaukasoina708n8s6l...(a)sci.fi (Petri Kaukasoina) wrote: > server 127.127.1.0 > fudge 127.127.1.0 stratum 11 > > Client 192.168.0.70 ntp.conf: > > server 192.168.0.30 iburst > driftfile /etc/ntp/drift Huh, after a second try with ntpdate -b -v 192.168.0.30 (-v be verbose) it works. ??? Don't know what does it mean, may be problems with network syncronisation? 1Gb LAN, new multicore machines. Much thanks. --- Bogdan
From: Petri Kaukasoina on 1 Feb 2008 14:01
<B.Yanchitsky(a)gmail.com> wrote: >On Feb 1, 8:08 pm, kaukasoina708n8s6l...(a)sci.fi (Petri Kaukasoina) >wrote: >> server 127.127.1.0 >> fudge 127.127.1.0 stratum 11 >> >> Client 192.168.0.70 ntp.conf: >> >> server 192.168.0.30 iburst >> driftfile /etc/ntp/drift > >Huh, after a second try with ntpdate -b -v 192.168.0.30 (-v be >verbose) it works. >??? >Don't know what does it mean, may be problems with network >syncronisation? 1Gb LAN, new multicore machines. It takes a few minutes before the ntpd server at 192.168.0.30 thinks it is syncronized to the local clock. iburst should make it faster. So change it at the server to this: server 127.127.1.0 iburst fudge 127.127.1.0 stratum 11 |