On Sun, 29 Mar 2009, Arnold Schekkerman wrote: > On 28-03-09 10:28, David J Taylor wrote: >> On my own system, the following nodes are incorrectly showing a >> leap-second for April 1st: >> dns0.rmplc.co.uk >> ntp1.arse.org >> ntpt1.core.theplanet.net >> calx.pulsewidth.org.uk >> scarlett.lon.rewt.org.uk > > On my system (st.3), the following node incorrectly shows a leap-second: > ntp2.hro.nl > This system is stratum 2 and in the pool, but blocks ntpq, so I don't know > which st.1 is spreading the leap info. > > I now block replies with a leap-second flag set with the following rules: > iptables -I dynNTP -m u32 --u32 "0>>22&0...@8>>24&0xC7=0x84" -j DROP > iptables -I dynNTP -m u32 --u32 "0>>22&0...@8>>24&0xC7=0x44" -j DROP > > When a leap second occurs, I'll remove the rules manually. > > Now my system cleared the leap_flag again :-) > > Arnold > Hi,
I operate 62.84.188.34 (scarlett.lon.rewt.org.uk), do you know if there are common stratum 1 servers in the above? I can list the time sources my ntpd is configured to use if needed. Regards, J _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
