I have IPv6 enabled and working, all tests pass on test-ipv6.com but the google ipv6 test fails. Google search is very slow to load pages so I tried ping and tracert with these results.
Pinging www.google.co.uk [2a00:1450:4009:808::1017] with 32 bytes of data:
Reply from 2a00:1450:4009:808::1017: TTL expired in transit.
Reply from 2a00:1450:4009:808::1017: TTL expired in transit.
Reply from 2a00:1450:4009:808::1017: TTL expired in transit.
Reply from 2a00:1450:4009:808::1017: TTL expired in transit.
Ping statistics for 2a00:1450:4009:808::1017:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Tracing route to www.google.co.uk [2a00:1450:4009:808::1017]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 2a02:390:5fb0:0:204:edff:fe3a:3ef1
2 35 ms 34 ms 35 ms 2a02:390:ffff:ffff:ffff:ffff:ffff:fffc
3 34 ms 34 ms 34 ms 2a02:390:0:ff00:ceef:48ff:fed1:53c0
4 64 ms 47 ms 47 ms 2a02:390:0:ff02::1
5 34 ms 35 ms 34 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
6 34 ms 34 ms 33 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
7 34 ms 34 ms 34 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
8 35 ms 34 ms 34 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
9 34 ms 34 ms 35 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
10 35 ms 35 ms 41 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
11 35 ms 35 ms 34 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
12 35 ms 34 ms 35 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
13 35 ms 35 ms 34 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
14 35 ms 34 ms 34 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
15 35 ms 35 ms 35 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
16 35 ms 34 ms 35 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
17 35 ms 34 ms 34 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
18 35 ms 34 ms 35 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
19 35 ms 35 ms 35 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
20 35 ms 35 ms 35 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
21 35 ms 35 ms 36 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
22 35 ms 35 ms 36 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
23 35 ms 36 ms 35 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
24 36 ms 36 ms 36 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
25 36 ms 36 ms 35 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
26 37 ms 35 ms 35 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
27 35 ms 35 ms 36 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
28 35 ms 36 ms 35 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
29 36 ms 36 ms 36 ms 2a02:390:0:fffb:202:17ff:fe6a:b01b
30 36 ms 36 ms 36 ms 2a02:390:0:fffb:218:74ff:fe1e:ef00
Trace complete.
Something is obviously wrong. Is anyone else seeing this or can someone point me in the right direction to resolve the issue please?
Jane
http://ipv6test.google.com gives me the interesting result of:
QuoteReady for the future of the Internet?
No problems detected.
You don't have IPv6, but you shouldn't have problems on websites that add IPv6 support.
Saying I don't have IPv6 is forgivable with a Mac, it's got an oddity about how it connects to a dual-stack site, but the message doesn't make sense :dunno:
ping6 www.google.co.uk just gives no output, with 100% packet loss when I Ctrl-C it.
traceroute6 www.google.co.uk behaves like yours- it goes around in circles (though with different addresses) and gives up after 64 hops.
Exactly. When I investigated 'TTL expired in transit' one thread did mention something about a 'routing loop' which is what seems to be going on here.
:dunno:
Jane
In case it means anything to anybody, the first dozen hops from my traceroute are:
traceroute6 www.google.co.uk
traceroute6 to www.google.co.uk (2a00:1450:4009:809::101f) from <my IP>, 64 hops max, 12 byte packets
1 2a02:390:6f0c:1:12bf:48ff:fed3:e998 0.363 ms 0.309 ms 0.261 ms
2 2a02:390:ffff:ffff:ffff:ffff:ffff:fffe 22.221 ms 10.243 ms 9.464 ms
3 2a02:390::ff00:ceef:48ff:fed1:53c0 9.527 ms 9.537 ms 10.082 ms
4 2a02:390:0:ff02::1 9.782 ms 9.807 ms 9.708 ms
5 2a02:390::fffb:202:17ff:fe6a:b01b 9.569 ms 9.574 ms 9.483 ms
6 2a02:390::fffb:218:74ff:fe1e:ef00 9.751 ms 9.574 ms 9.685 ms
7 2a02:390::fffb:202:17ff:fe6a:b01b 9.716 ms 9.981 ms 9.768 ms
8 2a02:390::fffb:218:74ff:fe1e:ef00 10.217 ms 9.900 ms 9.934 ms
9 2a02:390::fffb:202:17ff:fe6a:b01b 9.968 ms 9.933 ms 9.971 ms
10 2a02:390::fffb:218:74ff:fe1e:ef00 10.148 ms 10.182 ms 9.878 ms
11 2a02:390::fffb:202:17ff:fe6a:b01b 10.594 ms 9.987 ms 10.007 ms
12 2a02:390::fffb:218:74ff:fe1e:ef00 10.226 ms 10.124 ms 10.284 ms
Doesn't take long to get into a loop!
I think those 2a02:309 addresses belong to IDNet, if so then it looks like the problem may be with them.
That's interesting Bill. I hope someone from IDNet will come along and see this so that we can get their thoughts. :fingers:
Not sure what's going on my router has just need a reboot to get any IPv6 access. IPv6 Test is now showing 10/10 , if you go to 'Other IPv6 Sites' google.com is not reachable currently.
Hi all, we have found what was causing this problem and have now fxied it.
Thanks Simon, much more sensible results now :thumb: