On Sun, Jun 04, 2023 at 12:07:44PM +0200, Torsten Wolf wrote:
Not sure why the Reach value for the PPS source is 113. A few minuts later
that value increased to 372, just to go down again afterwards.
That might be due to changing offset between GPS and PPS. Try
adjusting the offset option to make it closer to the middle as
explained in the FAQ.
Local address : 192.168.1.105 (C0A80169)
Leap status : Normal
Version : 4
Mode : Server
Stratum : 2
Poll interval : 7 (128 seconds)
Precision : -25 (0.000000030 seconds)
Root delay : 0.000778 seconds
Root dispersion : 0.269699 seconds
Reference ID : C0A80169 ()
Reference time : Sun Jun 04 10:00:57 2023
Offset : -0.142506495 seconds
Peer delay : 0.000236495 seconds
Peer dispersion : 0.000000898 seconds
Response time : 0.000178912 seconds
Jitter asymmetry: +0.00
NTP tests : 111 111 1110
The test D is failing. That's the loop detection. The Reference ID is
the same as the local address, i.e. the client is polling a server
which seems to be synchronized to the client. As this happens with all
NTP servers and the peer delay is very short, I think it might be a
firewall in local network redirecting NTP requests to itself.