Interesting.
I added an input rule to allow outside udp to the masq machine on 123,
and now I see
ntpdate 131.216.18.4
13 Dec 11:33:50 ntpdate[19926]: adjust time server 131.216.18.4 offset
0.005303 sec
I though I had tried enabling 123, but I may have only done it for
inside traffic (actually,
Henrique M Holschuh wrote:
>
> On Mon, 13 Dec 1999, Dan Hugo wrote:
> > $ntptrace tock.cs.unlv.edu
> > tock.CS.UNLV.EDU: stratum 2, offset 0.853196, synch distance 0.04726
> > usno.pa-x.dec.com: stratum 1, offset 0.842812, synch distance 0.02371,
> > refid 'USNO'
>
> Those offset lines are wor
On Mon, Dec 13, 1999 at 08:45:04AM -0200, Henrique M Holschuh wrote:
> Don't kill tcp or udp packets from/to the ntp service port, nor delay them.
> When in doubt, try ntpq -p to "ping" the servers.
This will work even if the ntp ports are blocked by ipchains. Be sure
port 123 is accessable thro
On Mon, 13 Dec 1999, Dan Hugo wrote:
> $ntptrace tock.cs.unlv.edu
> tock.CS.UNLV.EDU: stratum 2, offset 0.853196, synch distance 0.04726
> usno.pa-x.dec.com: stratum 1, offset 0.842812, synch distance 0.02371,
> refid 'USNO'
Those offset lines are worrisome. NTP does not deal well with large offse
Greetings-
I have been using xntpd to keep some machines on time.
I recently switched to a different machine (PPro, Debian 2.1+updates,
kernel 2.2.1) to handle masquerading and xntpd (etc...), but I just
noticed that xntpd doesn't do anything any longer (okay, I changed the
machine from ppc to pp
5 matches
Mail list logo
