I have an ntpd ver. 4.2.8p15 that gets its time from the Pool Project using "pool pool.ntp.org". I don't understand why it will sometimes associate with a stratum-1 peer using a 64 s poll interval, never backing off to 1024 s, while using a 1024 s poll interval with all other peers. It's not always the same IP address so presumably not always the same peer. If I remember correctly, every "problem" peer has had a .GPS. refid.
The only practical problem I see with this is more traffic between my host and the stratum-1 peer. That's fine with me, but not fair to the peer. I don't see an issue with the uplink. The effective rate up/down is 800 Mbit/s (speedtest-cli). Connections to peers are under 50 ms delay and under 1 ms jitter. Reach, delay, offset, and jitter for the "problem" peer are no different from the others. In fact the "problem" peer is generally a member of the survivor list, and is sometimes the sys_peer. What events in the log, or variables on the association, should I be looking at to understand how this is happening? -- This is questions@lists.ntp.org Subscribe: questions+subscr...@lists.ntp.org Unsubscribe: questions+unsubscr...@lists.ntp.org
