OpenNTPD on pfSense. Clients dont sync
-
ive got the openntpd package installed.
ive enabled openntpd, and selected the interface to listen on as LAN.
ive created a firewall rule on the LAN tab. –->
Proto: TCP/UDP
Source: LAN Net
Port: *
Destination: LAN address
Port: 123
Gateway: *pfsense has had an uptime of over 6 hours.
when i run "ntpdate -d 192.168.2.1" on a debian box on the LAN; i get this:
26 Jan 13:54:52 ntpdate[19366]: ntpdate 4.2.4p8@1.1612-o Sat Aug 7 00:36:25 UTC 2010 (1) Looking for host 192.168.2.1 and service ntp host found : 192.168.2.1 transmit(192.168.2.1) receive(192.168.2.1) transmit(192.168.2.1) receive(192.168.2.1) transmit(192.168.2.1) receive(192.168.2.1) transmit(192.168.2.1) receive(192.168.2.1) transmit(192.168.2.1) 192.168.2.1: Server dropped: Leap not in sync server 192.168.2.1, port 123 stratum 2, precision -21, leap 11, trust 000 refid [192.168.2.1], delay 0.02573, dispersion 0.00000 transmitted 4, in filter 4 reference time: d0eb10e1.df5bafff Wed, Jan 26 2011 13:30:09.872 originate timestamp: d0eb16b1.ee0e5fff Wed, Jan 26 2011 13:54:57.929 transmit timestamp: d0eb16b1.b9e96c3f Wed, Jan 26 2011 13:54:57.726 filter delay: 0.02583 0.02573 0.02579 0.02574 0.00000 0.00000 0.00000 0.00000 filter offset: 0.203613 0.203632 0.203605 0.203621 0.000000 0.000000 0.000000 0.000000 delay 0.02573, dispersion 0.00000 offset 0.203632 26 Jan 13:54:57 ntpdate[19366]: no server suitable for synchronization found
on a windows 7 machine it tells me:
An error occured when windows was synchronizing with 192.168.2.1someone have an idea why nothing will sync ?
-
Usually windows will complain on startum levels.
I think the fix is to either tell windows to be more detailed or to tell openntpd to service windows with a diff stratum….still have a vague memory on it. -
One thing that would help, if we can somehow enable logging to send the OpenNTPD logs to the OpenNTPD tab under Status:System Logs. I dont think i've ever seen any entries even with 1.2.3. This way we can see if the client is connecting or not.
-
Cino;
yeah in 2.0, the logs dont populate either. ive never seen anything under the openntp tab. -
Not having any problem here.
ntpdate -d 192.168.1.253
27 Jan 15:58:23 ntpdate[5421]: ntpdate 4.2.4p8@1.1612-o Fri Apr 9 00:28:41 UTC 2010 (1)
Looking for host 192.168.1.253 and service ntp
host found : pfsense.local.lan
transmit(192.168.1.253)
receive(192.168.1.253)
transmit(192.168.1.253)
receive(192.168.1.253)
transmit(192.168.1.253)
receive(192.168.1.253)
transmit(192.168.1.253)
receive(192.168.1.253)
transmit(192.168.1.253)
server 192.168.1.253, port 123
stratum 3, precision -21, leap 00, trust 000
refid [192.168.1.253], delay 0.02603, dispersion 0.00000
transmitted 4, in filter 4
reference time: d0ec62eb.98a657ff Thu, Jan 27 2011 15:32:27.596
originate timestamp: d0ec68ff.c31adfff Thu, Jan 27 2011 15:58:23.762
transmit timestamp: d0ec68ff.bdaed56b Thu, Jan 27 2011 15:58:23.740
filter delay: 0.02637 0.02608 0.02609 0.02603
0.00000 0.00000 0.00000 0.00000
filter offset: 0.021008 0.020961 0.020924 0.020968
0.000000 0.000000 0.000000 0.000000
delay 0.02603, dispersion 0.00000
offset 0.02096827 Jan 15:58:23 ntpdate[5421]: adjust time server 192.168.1.253 offset 0.020968 sec
That is from my ubuntu box, I turn off built in time stuff on my window clients and run true ntp.. And it has no issues.
ntpq> pe
remote refid st t when poll reach delay offset jitter*pfsense.local.l 221.107.86.229 3 u 754 1024 377 0.455 22.233 34.308
If I recall correctly – this
"leap 11"Means your server is not in sync, so no your client will not sync to it. You need to figure out why your server is not sync'd -- yup logs would help!! I wish they would just go with the standard full ntpd vs that openntpd crap ;)
doesnt freebsd come with ntpd, whey does pfsense run openntpd vs and actual full ntp server?