On occasion, I have been able to successfully run a traceroute to an ipv6 website. However, it usually fails after partial success. This is to sites for which all the other daily tests have succeeded. Can anyone tell me why?
Here is today's example:
traceroute to 2610:148:fd8f:d7fc:203:baff:fe8f:29d (2610:148:fd8f:d7fc:203:baff:fe8f:29d) from 2001:470:8:b57:230:1bff:feb5:9a1d, 30 hops max, 16 byte packets
1 2001:470:8:b57::1 (2001:470:8:b57::1) 2.221 ms 2.267 ms 4.24 ms
2 ratcheer-1.tunnel.tserv13.ash1.ipv6.he.net (2001:470:7:b57::1) 43.137 ms 44.029 ms 42.174 ms
3 gige-g4-12.core1.ash1.he.net (2001:470:0:90::1) 43.285 ms 40.935 ms 46.249 ms
4 10gigabitethernet1-1.core1.dal1.he.net (2001:470:0:3b::1) 75.376 ms 81.666 ms 75.439 ms
5 10gigabitethernet5-4.core1.atl1.he.net (2001:470:0:1b6::2) 76.723 ms 75.654 ms 75.136 ms
6 2001:470:1:124::2 (2001:470:1:124::2) 74.868 ms 75.815 ms 75.173 ms
7 rich-gateway-rtr-to-sox-v6.8.4.1.0.0.1.6.2.ip6.arpa (2610:148:1f02:c2cc::2) 89.747 ms 89.422 ms 90.659 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Tim
It's not just you
traceroute6 to 2610:148:fd8f:d7fc:203:baff:fe8f:29d (2610:148:fd8f:d7fc:203:baff:fe8f:29d) from 2001:470:c27d:e000:20c:29ff:fe8a:1618, 64 hops max, 12 byte packets
1 *
2001:470:c27d:d000:2e0:81ff:fe79:f4c4 1.145 ms 0.869 ms
2 servicespring-1.tunnel.tserv9.chi1.ipv6.he.net 41.587 ms 40.855 ms 41.000 ms
3 gige-g3-4.core1.chi1.he.net 38.285 ms 37.940 ms 46.929 ms
4 10gigabitethernet7-2.core1.nyc4.he.net 57.657 ms 55.619 ms 55.555 ms
5 10gigabitethernet2-3.core1.ash1.he.net 61.700 ms 69.850 ms 69.569 ms
6 10gigabitethernet1-1.core1.dal1.he.net 78.613 ms 88.372 ms 78.519 ms
7 10gigabitethernet5-4.core1.atl1.he.net 101.171 ms 105.869 ms 102.310 ms
8 2001:470:1:124::2 94.782 ms 95.003 ms 95.331 ms
9 rich-gateway-rtr-to-sox-v6.8.4.1.0.0.1.6.2.ip6.arpa 87.384 ms 87.782 ms 86.967 ms
10 *^C
It took a long time to start tracing though...
Its because some people do not follow the RFC's and break basic troubleshooting tools!
Many traceroutes will fail on the ipv4 network as well. This is nothing new at all.. Its hard get a full trace to lots and lots of locations.. Trace to tunnelbroker.net be it ipv4 or ipv6 and it fails.
9 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 84.031 ms 88.792 ms 89.332 ms
10 10gigabitethernet1-1.core1.fmt1.he.net (72.52.92.109) 341.670 ms 342.332 ms 341.682 ms
11 * * *
12 * * *
5 10gigabitethernet4-4.core1.sjc2.he.net (2001:470:0:1b4::1) 86.798 ms 86.317 ms 87.482 ms
6 10gigabitethernet1-1.core1.fmt1.he.net (2001:470:0:2f::1) 101.654 ms 87.109 ms 95.878 ms
Yup, I've seen the same in my daily tests. The most problematic are the traceroute and the reverse resolution tests. Some routers just won't respond to ICMP at all, or ICMP will be the first traffic type to be dropped on a busy router. And many sites don't seem to be registering PTR records.