You guys are going to think I'm outta my mind.
FreeBDSD v13.3, using the base-included NTP, ntpd 4.2.8p16-a (1).
/etc/ntp.conf
/etc/rc.conf
Fired up the daemon with this:
after some time
ntpq -pn
The ntp daemon is clearly doing its client duty.
My problem: The ntp daemon will not act as a server at all. It refuses to respond to LAN time queries from any of my other devices. On my Windows machine I'm using "NTPTool" and it gets no response to ntp server queries. When I use NTPTool to bypass the FreeBSD ntp server it receives proper time responses.
I'm of the opinion that the base-installed ntp daemon *only* works as a client and not as a server. I've spent the afternoon reading how-tos dating back for years and none of the declarative, "This works, do this.", work. None. Nada. Zilch.
Even the FreeBSD handbook claims the ntp daemon can act as a local network time reference server...but it doesn't explain how to do it.
What am I doing wrong?
FreeBDSD v13.3, using the base-included NTP, ntpd 4.2.8p16-a (1).
/etc/ntp.conf
Code:
tos minclock 5 maxclock 8
pool clock.isc.org iburst
pool time.nist.gov iburst
# allow unrestricted access from the localhost
restrict 10.0.0.1/24 nomodify notrap
# ignore all interfaces...
interface ignore wildcard
# except these
interface listen 10.0.0.1
/etc/rc.conf
Code:
ntpd_enable="YES"
ntpd_sync_on_start="YES"
Fired up the daemon with this:
/etc/rc.d/ntpd start
after some time
ntpq -pn
Code:
remote refid st t when poll reach delay offset jitter
==============================================================================
clock.isc.org .POOL. 16 p - 64 0 0.000 +0.000 0.000
time.nist.gov .POOL. 16 p - 64 0 0.000 +0.000 0.000
*132.163.96.2 .NIST. 1 u 27 64 377 14.555 -3.197 3.607
+64.62.194.189 206.55.64.77 3 u 31 64 77 35.400 -2.106 1.401
+204.93.207.11 206.55.64.77 3 u 25 64 77 33.160 -8.114 2.155
+64.62.194.188 206.55.64.76 3 u 25 64 77 35.571 -3.736 2.221
+132.163.96.1 .NIST. 1 u 29 64 37 13.277 -1.833 1.328
The ntp daemon is clearly doing its client duty.
My problem: The ntp daemon will not act as a server at all. It refuses to respond to LAN time queries from any of my other devices. On my Windows machine I'm using "NTPTool" and it gets no response to ntp server queries. When I use NTPTool to bypass the FreeBSD ntp server it receives proper time responses.
I'm of the opinion that the base-installed ntp daemon *only* works as a client and not as a server. I've spent the afternoon reading how-tos dating back for years and none of the declarative, "This works, do this.", work. None. Nada. Zilch.
Even the FreeBSD handbook claims the ntp daemon can act as a local network time reference server...but it doesn't explain how to do it.
What am I doing wrong?
Last edited by a moderator: