Can a NTP Server escape the falseticker status?

Solution 1:

NTP falsetickers are statistical outliers in the last few time stamps. The status can change when the algorithms evaluate new data. You don't have the 4+ NTP servers required to reliably detect falsetickers. That may not be a problem if you don't have demanding requirements, could just use one decent performing NTP server.

Pay attention to the magnitude of the statistics. An offset of 180 ms is enormous when error from delay and jitter is single digit ms.

192.168.1.6 with refid LOCL is a little unusual. Undisciplined local clock pointing to self should not be used. But usually the LOCL driver is invoked with config lines matching server 127.127.1. Is that a remote NTP server? If remote, and you are overriding the refid string in ntpd.conf, don't.

On some lightly loaded host, configure ntpd or chrony to add additional references from internet sources. As a test, although a diverse source list is a great start if you wanted to build stratum 2 NTP servers.

server 192.168.1.5 iburst
server 192.168.1.6 iburst
pool 2.pool.ntp.org iburst
server time.cloudflare.com iburst
server time.facebook.com iburst

Anything flagged as a falseticker in this local plus internet configuration likely is a real outlier.

Your NTP servers on the LAN should be very close to each other, better than 10 ms. They should reference each other. For example, configure the .6 appliance to reference .5 as a NTP source, and vice versa.