You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a sense, a KoD RATE response is similar to a lack of response -- it provides no time information. In another sense, it's distinct, as it indicates there is a functioning NTP server responding in a timely, if useless, fashion.
Perhaps for scoring purposes it would make sense to treat a RATE response as a milder negative bump than a lack of response, and for offset graphing purposes, treat it similarly to a a non-response, that is, no offset data to graph.
abh
added a commit
to ntppool/monitor
that referenced
this issue
Aug 14, 2023
track in the monitor more explicitly that a kiss code was returned
don't use KoD offsets when graphing
(alternatively don't log the offset when a KissCode was returned)
https://community.ntppool.org/t/do-not-use-offset-value-from-kod-responses-in-offset-score-graphs/2988/
The text was updated successfully, but these errors were encountered: