John Winters kirjoitti:
I run a couple of NTP pool servers, one over IPv4 and one over IPv6.
(Well, actually they're the same server.)
My IPv4 one is currently showing as fine in the monitor, but the IPv6
one has allegedly been incommunicado since about 08:00 GMT today.
The thing is, I can still query it fine over IPv6 from a couple of
different sites. Anyone else seeing a failure of IPv6 traffic?
Works fine here. What's the IPv6 address of your server?
Can you ping6 ntppool.net? That works from here. How about traceroute6
to that address? Here's what I see from Gandi:
$ traceroute6 ntppool.net -q1
traceroute to ntppool.net (2607:f238:2::4), 30 hops max, 80 byte packets
1 2001:4b98:dc0:41::250 (2001:4b98:dc0:41::250) 1.917 ms
2 p252-core4-d-ip6.paris.gandi.net (2001:4b98:1f::c4d3:181) 0.916 ms
3 2001:4b98:1f::c1c4:1 (2001:4b98:1f::c1c4:1) 1.023 ms
4 2001:4b98:dc1::228:230 (2001:4b98:dc1::228:230) 80.091 ms
5 10gigabitethernet2-2.core1.ash1.he.net (2001:504:0:2::6939:1)
83.866 ms
6 xe-0.equinix.asbnva01.us.bb.gin.ntt.net (2001:504:0:2::2914:1)
82.935 ms
7 ae-6.r20.asbnva02.us.bb.gin.ntt.net (2001:418:0:2000::1cd) 82.231 ms
8 ae-2.r21.lsanca03.us.bb.gin.ntt.net (2001:418:0:2000::1f6) 146.174 ms
9 ae-2.r05.lsanca03.us.bb.gin.ntt.net (2001:418:0:2000::14e) 149.397 ms
10 xe-0-2-0-3.r05.lsanca03.us.ce.gin.ntt.net (2001:418:4000:5000::2e)
152.725 ms
11 xe9-4.hr01.lax2.phyber.com (2607:f238:0:6::2) 146.491 ms
12 2607:f238:0:10::2 (2607:f238:0:10::2) 153.110 ms
13 2607:f238:2::4 (2607:f238:2::4) 149.025 ms !X
At the moment, the probability of some IPv6 routing hiccup somewhere
along the route is much higher than the IPv6 monitoring malfunctioning.
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
