Hi, I have trouble making this server broadcast time, and I'm not sure what I'm doing wrong- AFAIK it should be working. The procedure I'm following is from a Debian Admin guide located here: http://www.debianadmin.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html
They won't even update from each other. Would someone look this over & see if it's obvious what the problem could be? The server that should be providing time is Debian Lenny, "Bascule". It provides routing on as many networks as are detailed in the config. Each network is allowed to query time, and is available from it's own address on each network. It's ntp package is this version: ntp/lenny uptodate 1:4.2.4p4+dfsg-8lenny3 = = = = = This is it's config file: # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. statsdir /var/log/ntpstats/ # Debug- log everything logconfig =all logfile /var/log/ntp.log statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable # You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example server clock.nyc.he.net dynamic # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will # pick a different set every time it starts up. Please consider joining the # pool: <http://www.pool.ntp.org/join.html> #server 0.debian.pool.ntp.org iburst dynamic #server 1.debian.pool.ntp.org iburst dynamic #server 2.debian.pool.ntp.org iburst dynamic #server 3.debian.pool.ntp.org iburst dynamic # Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for # details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions> # might also be helpful. # # Note that "restrict" applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers. # By default, exchange time with everybody, but don't allow configuration. #restrict -4 default kod notrap nomodify nopeer noquery #restrict -6 default kod notrap nomodify nopeer noquery restrict 172.27.100.0 mask 255.255.255.0 nomodify notrap restrict 172.27.101.0 mask 255.255.255.0 nomodify notrap restrict 10.15.30.0 mask 255.255.255.0 nomodify notrap restrict 10.15.60.0 mask 255.255.255.0 nomodify notrap restrict 10.15.90.0 mask 255.255.255.0 nomodify notrap restrict 10.15.120.0 mask 255.255.255.0 nomodify notrap restrict 10.15.150.0 mask 255.255.255.0 nomodify notrap restrict 10.15.180.0 mask 255.255.255.0 nomodify notrap restrict 10.15.210.0 mask 255.255.255.0 nomodify notrap restrict 10.90.20.0 mask 255.255.255.0 nomodify notrap restrict 10.90.40.0 mask 255.255.255.0 nomodify notrap restrict 10.90.60.0 mask 255.255.255.0 nomodify notrap # Local users may interrogate the ntp server more closely. restrict 127.0.0.1 restrict ::1 # Clients from this (example!) subnet have unlimited access, but only if # cryptographically authenticated. #restrict 192.168.123.0 mask 255.255.255.0 notrust # If you want to provide time to your local subnet, change the next line. # (Again, the address is an example only.) broadcast 172.27.100.10 broadcast 172.27.101.10 broadcast 10.15.30.10 broadcast 10.15.60.10 broadcast 10.15.90.10 broadcast 10.15.120.10 broadcast 10.15.150.10 broadcast 10.15.180.10 broadcast 10.15.210.10 broadcast 10.90.20.10 broadcast 10.90.40.10 broadcast 10.90.60.10 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! #disable auth #broadcastclient = = = = = = = = = = The server I'm testing against is Debian Squeeze. It's version is this: ntp/squeeze uptodate 1:4.2.6.p2+dfsg-1+b1 When I try to update, it will from the internet, but not from the server it should update from. r...@planck:~# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== Bascule.san.sss .INIT. 16 u 1069 1024 0 0.000 0.000 0.000 r...@planck:~# ntpq -p clock.nyc.he.net remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) LOCAL(0) 10 l 14 64 377 0.000 0.000 0.000 *HOPF_S(0) .CDMA. 0 l 8 16 377 0.000 0.000 0.000 That server is reachable: r...@planck:~# ping Bascule PING Bascule.san.sss.local (10.15.90.10) 56(84) bytes of data. 64 bytes from Bascule.san.sss.local (10.15.90.10): icmp_req=1 ttl=64 time=0.080 ms 64 bytes from Bascule.san.sss.local (10.15.90.10): icmp_req=2 ttl=64 time=0.096 ms 64 bytes from Bascule.san.sss.local (10.15.90.10): icmp_req=3 ttl=64 time=0.094 ms 64 bytes from Bascule.san.sss.local (10.15.90.10): icmp_req=4 ttl=64 time=0.065 ms ^C --- Bascule.san.sss.local ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2999ms rtt min/avg/max/mdev = 0.065/0.083/0.096/0.016 ms r...@planck:~# I see this in the log: r...@planck:~# 20 Nov 02:13:50 ntpd[2753]: bind(23) AF_INET6 fe80::baac:6fff:fe80:3a18%6#123 flags 0x11 failed: Cannot assign requested address 20 Nov 02:13:50 ntpd[2753]: unable to create socket on bond0 (20) for fe80::baac:6fff:fe80:3a18#123 20 Nov 02:13:50 ntpd[2753]: failed to init interface for address fe80::baac:6fff:fe80:3a18 r...@planck:~# This one's config file looks like this: # cat /etc/ntp.conf # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. statsdir /var/log/ntpstats/ # Debug- log everything logconfig =all logfile /var/log/ntp.log statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable # You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example server Bascule.san.sss.local dynamic server Bascule dynamic # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will # pick a different set every time it starts up. Please consider joining the # pool: <http://www.pool.ntp.org/join.html> #server 0.debian.pool.ntp.org iburst #server 1.debian.pool.ntp.org iburst #server 2.debian.pool.ntp.org iburst #server 3.debian.pool.ntp.org iburst # Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for # details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions> # might also be helpful. # # Note that "restrict" applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers. # By default, exchange time with everybody, but don't allow configuration. restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery # Local users may interrogate the ntp server more closely. restrict 127.0.0.1 restrict ::1 # Clients from this (example!) subnet have unlimited access, but only if # cryptographically authenticated. #restrict 192.168.123.0 mask 255.255.255.0 notrust # If you want to provide time to your local subnet, change the next line. # (Again, the address is an example only.) #broadcast 192.168.123.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! #disable auth #broadcastclient Thanks, -C _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
