On Saturday 15 November 2008 14:13:44 Olaf Mueller wrote:
Anne Wilson wrote:
On Saturday 15 November 2008 10:41:14 Olaf Mueller wrote:
Anne Wilson wrote:
No, the server is on a fixed IP, internally and externally.
Ok, here is my config file, hope this helps. There was an option in the 'restrict default' line that I had to remove for working properly, but I couldn't remember what it was.
I wonder if it was ipv6 lines? I have
# cat /etc/ntp.conf restrict default kod nomodify notrap nopeer noquery restrict 127.0.0.1 restrict 192.168.0.0 mask 255.255.255.0 nomodify notrap restrict 0.de.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery restrict 1.de.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery restrict 2.de.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery restrict 3.de.pool.ntp.org mask 255.255.255.255 nomodify notrap noquery
restrict default kod nomodify notrap nopeer noquery restrict -6 default kod nomodify notrap nopeer noquery
server 127.127.1.0 server 0.de.pool.ntp.org server 1.de.pool.ntp.org server 2.de.pool.ntp.org server 3.de.pool.ntp.org
server 0.centos.pool.ntp.org server 1.centos.pool.ntp.org server 2.centos.pool.ntp.org server 127.127.1.0 # local clock
driftfile /var/lib/ntp/drift keys /etc/ntp/keys fudge 127.127.1.0 stratum 10 broadcastdelay 0.008
fudge 127.127.1.0 stratum 10 driftfile /var/lib/ntp/drift keys /etc/ntp/keys
I don't have a broadcastdelay line, as far as I can see.
You have fare more 'restricts' than I have, but apart from that the main difference seems to be the presence of two IPV6 lines. What do you think?
Anne