Hi All,
I'm connected to the London/UK pop and sometime in the last few days all my traceroute's are showing like this
root@web:~# traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2001:4860:0:1001::68) from 2001:470:1f09:282:208:74ff:fe46:a8f3, 30 hops max, 16 byte packets
1 gateway.ipv6.darkstar.be (2001:470:1f09:282::1) 2.655 ms 0.327 ms 0.378 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 2001:4860:0:1001::68 (2001:4860:0:1001::68) 28.801 ms 31.534 ms 28.306 ms
Nothing's changed inside my network, and it only seem's to happen going across the EU pop's - Seem's fine across the USA pop's
traceroute to tunnelbroker.net (2001:470:0:63::2) from 2001:470:1f09:282:208:74ff:fe46:a8f3, 30 hops max, 16 byte packets
1 gateway.ipv6.darkstar.be (2001:470:1f09:282::1) 4.029 ms 0.265 ms 0.202 ms
2 * * *
3 * * *
4 10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1) 87.966 ms 86.912 ms 86.039 ms
5 10gigabitethernet3-1.core1.sjc2.he.net (2001:470:0:33::1) 167.981 ms 171.179 ms 177.72 ms
6 gige-g1-1.core1.fmt1.he.net (2001:470:0:2f::1) 175.994 ms 166.405 ms 167.243 ms
7 tunnelbroker.net (2001:470:0:63::2) 171.838 ms 166.972 ms 198.934 ms
Any ideas? It's causing my reverse traceroute script to lag more than a little now days (had to take it off of my site for now).
FYI, contacted Google about this and our peering session in London. Waiting to hear back from them regarding this, so I don't have an ETA on a resolution right now.
Ok, they got their London peering with us fixed. I notice with a quick tunnel created that traceroute6 seems to kinda stop inside Google's network after their first hop. Running mtr behind the same tunnel gets a different result and actually reaches the site with 1 hop inside Google's network that has no results (just * * *). My guess is that Google is doing something with the traffic which would be outside of our control.
Thanks for the replies, doesn't explain why traces to tunnelbroker.net would do the same though?
Not a major issue, just I have a few scripts on my site for people to check their IPv6 connectivity so handy if it doesn't lag ;) Unless you know a way to make traceroute6 ignore the first 3 hops?
Cheers :)
Actually I wasn't getting that problem to ipv6.he.net with traceroute6 or mtr. I just double-checked right now and its still clean even from the tunnel-server itself. Can you retest?
1 gige-g4-6.core1.lon1.he.net 0.378 ms 0.246 ms 0.137 ms
2 10gigabitethernet2-3.core1.nyc4.he.net 69.463 ms 69.275 ms 69.308 ms
3 10gigabitethernet3-1.core1.sjc2.he.net 148.919 ms 148.485 ms 148.567 ms
4 gige-g1-1.core1.fmt1.he.net 148.874 ms 148.994 ms 148.897 ms
5 ipv6.he.net 148.875 ms 148.983 ms 149.038 ms
Very weird....
Checked from two different Linux boxes
root@web:~# traceroute6 tunnelbroker.net
traceroute to tunnelbroker.net (2001:470:0:63::2) from 2001:470:1f09:282:208:74ff:fe46:a8f3, 30 hops max, 16 byte packets
1 gateway.ipv6.darkstar.be (2001:470:1f09:282::1) 0.356 ms 0.261 ms 0.184 ms
2 * * *
3 * * *
4 10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1) 89.175 ms 85.923 ms 90.483 ms
5 10gigabitethernet3-1.core1.sjc2.he.net (2001:470:0:33::1) 164.462 ms 166.209 ms 165.848 ms
6 gige-g1-1.core1.fmt1.he.net (2001:470:0:2f::1) 178.423 ms 177.342 ms 173.228 ms
7 tunnelbroker.net (2001:470:0:63::2) 171.104 ms 165.076 ms 166.091 ms
gateway:~# traceroute6 tunnelbroker.net
traceroute to tunnelbroker.net (2001:470:0:63::2), 30 hops max, 40 byte packets
1 * * *
2 * * *
3 10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1) 91.600 ms 96.368 ms 96.352 ms
4 10gigabitethernet3-1.core1.sjc2.he.net (2001:470:0:33::1) 174.674 ms 174.660 ms 176.065 ms
5 gige-g1-1.core1.fmt1.he.net (2001:470:0:2f::1) 181.104 ms 181.199 ms 181.183 ms
6 tunnelbroker.net (2001:470:0:63::2) 179.645 ms 166.582 ms 166.714 ms
Maybe it's just me ???