My ipv6 ntp server at 2a01:4f8:110:4443::1fef is experiencing exactly
the same symptoms as Andreas (and also started exactly at the same time,
which indicates a bigger routing problem).
My traceroute to the monitoring stations looks quite similar. I tried to
use a UDP traceroute6 with destination port 123, but at least from FRA
to LAX it outputs the same numbers as the default ICMP traceroute6.
Differently to Andreas' traceroute I don't get a reply from one hop in
between (2001:504:13::11).
For reference:
root@spacys:~# traceroute -6 -UL -p123 -N1 ntppool.net
traceroute to ntppool.net (2607:f238:2::4), 30 hops max, 80 byte packets
1 2a01:4f8:110:4440::1 (2a01:4f8:110:4440::1) 3.504 ms 0.641 ms
0.573 ms
2 hos-tr4.juniper2.rz11.hetzner.de (2a01:4f8:0:11:4:0:11:2) 0.249 ms
0.232 ms 0.242 ms
3 hos-bb2.juniper4.ffm.hetzner.de (2a01:4f8:0:2::1:4) 6.056 ms 6.034
ms 6.059 ms
4 30gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1) 17.652
ms 6.991 ms 17.550 ms
5 10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1) 32.721
ms 24.093 ms 24.776 ms
6 10gigabitethernet10-4.core1.nyc4.he.net (2001:470:0:128::1) 97.687
ms 99.265 ms 100.118 ms
7 10gigabitethernet12-2.core1.lax1.he.net (2001:470:0:10e::1) 150.545
ms 150.435 ms 162.845 ms
8 10gigabitethernet1-3.core1.lax2.he.net (2001:470:0:72::2) 151.102
ms 150.259 ms 190.308 ms
9 * * *
10 2607:f238::cfab:1e01 (2607:f238::cfab:1e01) 156.633 ms 156.690 ms
156.707 ms
11 xe9-4.hr01.lax2.phyber.com (2607:f238:0:6::2) 156.793 ms 157.145
ms 157.028 ms
12 2607:f238:0:10::2 (2607:f238:0:10::2) 157.688 ms 156.952 ms 157.108 ms
13 2607:f238:2::4 (2607:f238:2::4) 156.978 ms !X 157.101 ms !X
157.025 ms !X
Another interesting fact is, that in turn, I can query the ntpdate from
Andreas, but I can get the traceroute only into his subnet.
traceroute to 2a01:238:43da:1c00::affe (2a01:238:43da:1c00::affe), 30
hops max, 80 byte packets
1 2a01:4f8:110:4440::1 (2a01:4f8:110:4440::1) 0.949 ms 1.679 ms
0.640 ms
2 hos-tr3.juniper2.rz11.hetzner.de (2a01:4f8:0:11:3:0:11:2) 0.188 ms
5.574 ms 0.289 ms
3 hos-bb2.juniper4.ffm.hetzner.de (2a01:4f8:0:2::1:4) 6.067 ms 6.060
ms 6.112 ms
4 morla.rzone.de (2001:7f8::1a44:0:2) 11.991 ms 7.044 ms 7.536 ms
5 xe-0-0-1.core-b30.as6724.net (2a01:238:0:30ad::1) 18.139 ms 18.852
ms 19.049 ms
6 te0-2-0-0.core-b2.as6724.net (2a01:238:0:b230::1) 18.767 ms 18.983
ms 18.839 ms
7 vl434.dcata-b17.as6724.net (2a01:238:b:217::2) 19.786 ms 19.615
ms 19.359 ms
8 extern.kwsoft.de (2a01:238:43da:1c00:a31b:6ffb:84e2:4ab5) 19.457
ms 19.565 ms 20.214 ms
9 * * *
10 * * *
Not sure, if this UDP traceroute is handled the same way as real NTP
packets by the routers, but probably worth a try.
Regards,
Helge
Am 27.06.2013 09:56, schrieb [email protected]:
Zitat von Ask Bjørn Hansen <[email protected]>:
Can you traceroute6 to ntppool.net from the server?
—
http://askask.com/
traceroute to ntppool.net (2607:f238:2::4), 30 hops max, 80 byte packets
1 extern.kwsoft.de (2a01:238:43da:1c00:a31b:6ffb:84e2:4ab5) 0.089
ms 0.047 ms 0.045 ms
2 be17.433.core-b1.as6724.net (2a01:238:b:117::1) 0.752 ms 0.696
ms 0.649 ms
3 xe-1-1-1.atuin.as6724.net (2a01:238:1:b1a3::2) 13.509 ms 13.464
ms 13.416 ms
4 30gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1) 18.321
ms 18.273 ms 18.227 ms
5 10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1) 32.159
ms 32.082 ms 36.017 ms
6 10gigabitethernet10-4.core1.nyc4.he.net (2001:470:0:128::1) 94.911
ms 99.375 ms 94.325 ms
7 10gigabitethernet12-2.core1.lax1.he.net (2001:470:0:10e::1)
158.216 ms 158.782 ms 154.732 ms
8 10gigabitethernet1-3.core1.lax2.he.net (2001:470:0:72::2) 157.668
ms 154.477 ms 154.423 ms
9 2001:504:13::11 (2001:504:13::11) 155.306 ms 166.488 ms 166.402 ms
10 2607:f238::cfab:1e01 (2607:f238::cfab:1e01) 155.285 ms 158.445
ms 156.375 ms
11 2607:f238:0:9::2 (2607:f238:0:9::2) 156.768 ms 153.461 ms
157.395 ms
12 2607:f238::cfab:1e0e (2607:f238::cfab:1e0e) 158.818 ms 154.777
ms 156.366 ms
13 2607:f238:2::4 (2607:f238:2::4) 161.303 ms !X 160.438 ms !X
158.773 ms !X
Looks good no?
And from another IPv6 enabled machine:
27 Jun 09:54:29 ntpdate[15674]: ntpdate [email protected] Tue Jun 5
20:12:12 UTC 2012 (1)
Looking for host 2a01:238:43da:1c00::affe and service ntp
transmit(2a01:238:43da:1c00::affe)
receive(2a01:238:43da:1c00::affe)
transmit(2a01:238:43da:1c00::affe)
receive(2a01:238:43da:1c00::affe)
transmit(2a01:238:43da:1c00::affe)
receive(2a01:238:43da:1c00::affe)
transmit(2a01:238:43da:1c00::affe)
receive(2a01:238:43da:1c00::affe)
transmit(2a01:238:43da:1c00::affe)
server 2a01:238:43da:1c00::affe, port 123
stratum 2, precision -20, leap 00, trust 000
refid [2a01:238:43da:1c00::affe], delay 0.02699, dispersion 0.00107
transmitted 4, in filter 4
reference time: d5766d4a.6a399ceb Thu, Jun 27 2013 9:50:34.414
originate timestamp: d5766e3b.ac1f1f9e Thu, Jun 27 2013 9:54:35.672
transmit timestamp: d5766e3b.ad3c16c7 Thu, Jun 27 2013 9:54:35.676
filter delay: 0.02699 0.04309 0.02705 0.02718
0.00000 0.00000 0.00000 0.00000
filter offset: -0.00502 -0.01305 -0.00508 -0.00520
0.000000 0.000000 0.000000 0.000000
delay 0.02699, dispersion 0.00107
offset -0.005021
27 Jun 09:54:37 ntpdate[15674]: adjust time server
2a01:238:43da:1c00::affe offset -0.005021 sec
So someone is on the way is dropping IPv6 ntp packets :-(
Regards
Andreas
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
