I'm a bit confused by what I am seeing in the logfiles when compared to the information found in the manpages and FAQ. I would appreciate if someone could provide some perspective.
I've set up OpenNTPD on a 4.3-current server (192.168.0.4), and the time has finally reached synchronization as best I can tell: server $ sudo tail /var/log/daemon May 24 17:38:17 server ntpd[32321]: adjusting clock frequency by 12.518122 to 37.282963ppm May 24 18:06:18 server ntpd[32321]: adjusting clock frequency by -3.055956 to 34.227007ppm May 24 18:34:19 server ntpd[32321]: adjusting clock frequency by 1.532853 to 35.759861ppm May 24 19:02:20 server ntpd[32321]: adjusting clock frequency by -1.548559 to 34.211301ppm May 24 19:30:21 server ntpd[32321]: adjusting clock frequency by 27.436873 to 61.648175ppm May 24 19:58:22 server ntpd[32321]: adjusting clock frequency by -16.620842 to 45.027332ppm May 24 20:26:24 server ntpd[32321]: adjusting clock frequency by -21.159011 to 23.868321ppm May 24 20:54:25 server ntpd[32321]: adjusting clock frequency by -8.922065 to 14.946257ppm May 24 21:22:26 server ntpd[32321]: adjusting clock frequency by 19.461742 to 34.407999ppm May 24 21:50:27 server ntpd[32321]: adjusting clock frequency by -14.422098 to 19.985901ppm server $ I also have a 4.3-current client on the same subnet (192.168.0.6) & switch (no firewalls involved), and see "Connection refused" in /var/log/daemon on the client's side: client $ sudo tail /var/log/daemon May 24 17:12:11 client dhclient[273]: DHCPACK from 192.168.0.1 May 24 17:12:11 client dhclient[273]: bound to 192.168.0.6 -- renewal in 43200 seconds. May 24 21:11:00 client ntpd[16786]: ntp engine ready May 24 21:11:00 client ntpd[16786]: recvfrom 192.168.0.4: Connection refused May 24 21:11:01 client savecore: no core dump May 24 21:29:45 client ntpd[8992]: ntp engine ready May 24 21:29:45 client ntpd[8992]: recvfrom 192.168.0.4: Connection refused May 24 21:29:46 client savecore: no core dump May 24 22:24:27 client ntpd[8992]: 0 out of 1 peers valid May 24 22:24:27 client ntpd[8992]: bad peer 192.168.0.4 (192.168.0.4) client $ The client has the following contents for its configuration files: client $ cat /etc/rc.conf.local ntpd_flags="-v" client $ cat /etc/ntpd.conf # $OpenBSD: ntpd.conf,v 1.8 2007/07/13 09:05:52 henning Exp $ # sample ntpd configuration file, see ntpd.conf(5) # Addresses to listen on (ntpd does not listen by default) #listen on * # sync to a single server #server ntp.example.org server 192.168.0.4 # use a random selection of 8 public stratum 2 servers # see http://support.ntp.org/bin/view/Servers/NTPPoolServers #servers pool.ntp.org client $ I saw in the archives someone else having a similar error, but no definitive reply. It appears that the server is sending out traffic correctly on port 123: server $ netstat -f inet -na Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) ip 0 0 *.* *.* 17 Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 224 192.168.0.6.22 192.168.0.125.43307 ESTABLISHED tcp 0 0 192.168.0.6.48455 192.168.0.4.22 ESTABLISHED tcp 0 0 192.168.0.6.22 192.168.0.125.44198 ESTABLISHED tcp 0 0 127.0.0.1.587 *.* LISTEN tcp 0 0 127.0.0.1.25 *.* LISTEN tcp 0 0 *.22 *.* LISTEN tcp 0 0 *.37 *.* LISTEN tcp 0 0 *.13 *.* LISTEN tcp 0 0 *.113 *.* LISTEN Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address (state) udp 0 0 127.0.0.1.512 *.* udp 0 0 192.168.0.6.32093 192.168.0.4.123 udp 0 0 *.514 *.* server $ I know that it can take some time for the client to synchronize with an NTP server, but the "Connection refused" message has me wondering if I have missed something else in the configuration. Any help would be appreciated. Thanks!
