<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
On 4/8/2024 18:51 PM, James Browning via users wrote:
<blockquote type="cite"
cite="mid:1865708398.144385.1712627465425@privateemail.com">
<pre class="moz-quote-pre" wrap="">I suspect for no valid reason at all that someone has placed a
packet filter near your machine; I also suspect it has been set
to some ridiculous criteria like 'drop all UDP port 123 packets
longer than 48-bytes.'
A tool like tcpdump should give you an idea of what NTP traffic
is actually on the wire versus what either end responds to. Not
sorry about being useless, you might want to wait for someone
else, or not the lag can be pretty bad.
</pre>
</blockquote>
<br>
Thanks. No packet filters in evidence, based both on my control of
the router, the fully functional NTP traffic, and the initializing
NTS traffic on port 4460 that appears during setup after restarting
ntpsec. And it's not blocked by my ISP -
<a class="moz-txt-link-freetext" href="https://www.xfinity.com/support/articles/list-of-blocked-ports">https://www.xfinity.com/support/articles/list-of-blocked-ports</a><br>
<br>
tcpdumps don't show anything 'interesting' really on either
timeservice port - steady flow of NTP traffic, no meaningful NTS
traffic (I have to imagine that the NTS traffic at initialization at
ntpd startup would be entirely broken if there were limits on the
port)<br>
<br>
It's a puzzle, that much I know.<br>
<br>
cheers,<br>
paul<br>
<pre class="moz-signature" cols="74">--
Paul Theodoropoulos
<a class="moz-txt-link-abbreviated" href="http://www.anastrophe.com">www.anastrophe.com</a></pre>
</body>
</html>