[lug] NTP Configuration

[Glenn Murray]

Ah ha.  So when I take down my firewall:

glenn/$ sudo ipchains -L
Chain input (policy ACCEPT):
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):
glenn/$ sudo ntpdate time-a.timefreq.bldrdoc.gov
 2 Oct 13:21:03 ntpdate[17007]: the NTP socket is in use, exiting
glenn/$ sudo /etc/init.d/ntp stop
Stopping NTP server: ntpd.
glenn/$ sudo ntpdate time-a.timefreq.bldrdoc.gov
 2 Oct 13:22:07 ntpdate[17010]: step time server 132.163.4.101 offset 15.438177 sec
glenn/$ sudo /etc/init.d/ntp restart
Restarting NTP server: ntpd... done.

So presumably ntpd can now set the system clock automatically.

Perhaps you could help with the ipchains rule; x.x.x.x is my machine.
I know that 132.163.4.101, 132.163.4.102, 132.163.4.103, and
132.163.4.104 are Boulder NIST time servers.  Is it better to have
four than one?

ipchains -A input -i eth0 -p tcp -s 132.163.4.101/30 123 -d x.x.x.x 123 -j ACCEPT

Thanks,
Glenn Murray
www.mines.edu/~gmurray/public_html/Welcome.html

On Tue, 2 Oct 2001, Kevin Fenzi wrote:
...
> You need to allow port 123 traffic from port 123 traffic (tcp)... 
...