Hi, On 06/30/2012 02:32 AM, Bill Waggoner wrote: > Just for grins I decided to check what I am getting this evening and > got the following results:
I did the same, but got some unexpected results. 4 out of 7 reachable peers are announcing the leap second, but my system decides 'leap_none'. Of course the 4 systems announcing leap are a minority with respect to all peers, but IMHO ntpd should ignore unreachable peers in the voting. For those wondering why I've so many unreachable peers: they are IPv4 peers with a firewall rule filtering leap 01 and leap 10 responses (so the last response for each peer was a leap_none response). This is from the time that only ONE (badly configured) peer could set a ntpd server to leap second mode. I did not implement this filtering in my IPv6 firewall rules. Associates 6009 and 6017 are also IPv4, so they will become unreachable as well when they start announcing the leap (in fact 6009 was unreachable for some minutes already). I'll wait and see what the voting will be when only leap indicating peers are reachable... This system is in the IPv6 pool only, and I will make sure it announces leap as well a few hours in advance. Arnold $ ntpq ntpq> associations ind assid status conf reach auth condition last_event cnt =========================================================== 1 6009 941a yes yes none candidate sys_peer 1 2 6010 931a yes yes none outlyer sys_peer 1 3 6011 941a yes yes none candidate sys_peer 1 4 6012 8011 yes no none reject mobilize 1 5 6013 9434 yes yes none candidate reachable 3 6 6014 931a yes yes none outlyer sys_peer 1 7 6015 941a yes yes none candidate sys_peer 1 8 6016 8023 yes no none reject unreachable 2 9 6017 961a yes yes none sys.peer sys_peer 1 10 6018 8023 yes no none reject unreachable 2 11 6019 8043 yes no none reject unreachable 4 12 6020 8023 yes no none reject unreachable 2 13 6021 8023 yes no none reject unreachable 2 14 6022 80e3 yes no none reject unreachable 14 15 6023 8023 yes no none reject unreachable 2 16 6024 8011 yes no none reject mobilize 1 17 6025 80a3 yes no none reject unreachable 10 18 6026 8023 yes no none reject unreachable 2 19 6027 8083 yes no none reject unreachable 8 ntpq> rv 6009 leap leap=00 ntpq> rv 6010 leap leap=01 ntpq> rv 6011 leap leap=01 ntpq> rv 6013 leap leap=01 ntpq> rv 6014 leap leap=01 ntpq> rv 6015 leap leap=00 ntpq> rv 6017 leap leap=00 ntpq> rv 0 leap leap=00 ntpq> rv associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer, version="ntpd [email protected] Sun Oct 17 13:45:13 UTC 2010 (1)", processor="i686", system="Linux/2.6.32-5-686", leap=00, stratum=3, precision=-20, rootdelay=37.570, rootdisp=61.990, refid=213.239.154.12, reftime=d3997f1c.07989c5a Sat, Jun 30 2012 15:35:24.029, clock=d3998294.ff62988c Sat, Jun 30 2012 15:50:12.997, peer=6017, tc=10, mintc=5, offset=-0.177, frequency=-109.157, sys_jitter=2.670, clk_jitter=1.030, clk_wander=0.069 ntpq> _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
