Quote:
|
What's hard to understand?
|
I'm confused about all this talk about the listen address. I had always left it unused unless attempting to serve out like I am now.
I already am running NTP as follows:
And I have rebooted my system.
Quote:
before any NTP server can serve clients.. it first must be totally synchronized with another time source, whether that's a remote server or a local timedelta sensor.. it doesn't mater.
|
Isn't that the point of this? (which has been running just fine for quite a long time)
Code:
server 0.ca.pool.ntp.org
server 1.ca.pool.ntp.org
server 2.ca.pool.ntp.org
I tried manually using rdate first on the NTP Server and than on the BSD2 machine.
on BSD1 came back with about 20 lines of:
(rdate -ncv 0.ca.pool.ntp.org)
rdate: Invalid cookie received, packet rejected
and ended with:
rdate: adjust local clock by 36.102187 seconds
on BSD2 it seemed to just fail:
(rdate -ncv 192.168.244.1)
rdate: Ignoring NTP server with alarm flag set
rdate: Unable to get a reasonable time estimate
Thanks for your help.
