NTP server showing "Not Considered" v26.1.6

[Greg_E]

I'm messing around in my lab firewall, just (finally) upgraded to current, and found something that may or may not be a problem.

In Services -> Network Time -> Status it is showing my GPS NTP server as "Not Considered"

I deleted the pool servers, all of which had a DNS issue and could not be found (a my end problem) and my local GPS NTP server was set to prefer, but no log entries that it has ever been connected. After a reboot it is reporting "Clock Unsynchronized"

I have verified that my local server is up, and that other clients are connecting. Not sure why this is happening.

I do see the firewall in the access logs of the NTP server, not sure why the firewall says unsync.

[Greg_E]

To add to this, it is syncing. I can see the counters change in the status screen as I refresh the page. "When" changes and eventually resets to a low number after about 64 seconds (which is where "POLL" is set). But it still says not considered. The log stops says it is unsync after a few minutes too, but never reports successful sync either.

[pfry]

The only things I can think of would be stratum (too high) or auth... but those aren't enumerated as a status. "Not Considered" does not appear in the NTP source. I assume it's a text representation of an ntpq peer status. So... what symbol ("Select Field" code from the URL) appears on the left edge of "ntpq -p"?