On 2023-12-19 22:16, joe a wrote:
On 12/19/2023 16:02:42, Carlos E. R. wrote:
On 2023-12-18 22:22, James Knott wrote:
On 12/18/23 03:40, Rodney Baker wrote:
systemd-timesyncd is not running.
As mentioned in another message, this is just an NTP client, not a server. My server is on my pfSense firewall/router.
There is no such thing.
The ntp daemon is always client and server. IIRC, it needs 3 other servers to compare to in order to get a good clock reference. Otherwise it will not be happy.
Perhaps terminology is at issue here. AFAIK the NTP daemon does not act as a "server" that is, advertising itself as an NTP server, to act as a time reference. At least by default.
It only acts as a client, for the device it is running on, providing an accurate time that it obtains from whatever source one enters into it's list of NTP servers.
While there can be several servers entered, as long as the first one entered responds "in time" (see what I did there???) the client accepts that an goes back to sleep.
To the best of my recollection.
You only need to tell another machine of the address of the first one, and the first one will instantly act as server. What I don't remember is if a machine on the LAN can broadcast a query for ntp servers. Of course, the machine has to know that its time is accurate, and for this it needs to compare its own time with other machines. I think the minimum is three. Where from can the daemon obtain external addresses of servers, I do not know. The dhcp server of the lan can publish them, I think. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)