Ticket ID: SIXXS #1212479 Ticket Status: Resolved PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)
Routing reaching most of the IPv6 internet
Shadow Hawkins on Thursday, 24 September 2009 10:33:10
Hello,
My tunnel is configured, but does not work when i try to connect to most of the IPv6 internet. I've tried both pinging and traceroute to www.kame.net, www.sixxs.net, ipv6.google.com and several other IPv6 Destinations.
tian$ traceroute6 ipv6.google.com
traceroute6 to ipv6.l.google.com (2001:4860:b004::68) from 2001:4830:1600:1d5::2, 30 hops max, 12 byte packets
1 gw-470.qas-01.us.sixxs.net 156.227 ms 153.72 ms 154.959 ms
2 sixxs-gw.hotnic.us.occaid.net 154.343 ms 154.205 ms 154.836 ms
3 iad0-b0-ge2.hotnic.net 154.579 ms 158.47 ms 154.933 ms
4 carpathia-gw.hotnic.net 162.203 ms 158.248 ms 163.442 ms
5 * * *
6 * * *
===== Trimmed =====
tian$ traceroute6 www.kame.net
traceroute6 to www.kame.net (2001:200::8002:203:47ff:fea5:3085) from 2001:4830:1600:1d5::2, 30 hops max, 12 byte packets
1 gw-470.qas-01.us.sixxs.net 151.913 ms 149.831 ms 154.258 ms
2 sixxs-gw.hotnic.us.occaid.net 150.694 ms 150.41 ms 150.874 ms
3 iad0-b0-ge2.hotnic.net 150.566 ms 150.4 ms 155.024 ms
4 carpathia-gw.hotnic.net 150.432 ms 150.463 ms 220.06 ms
5 xe-3-3.e3.iad1.cirn.net 161.713 ms 157.083 ms 156.573 ms
6 2001:4838:0:1::c:2 154.219 ms 154.4 ms 154.577 ms
7 * * *
===== Trimmed =====
So I wonder if there is a trouble in my configuration, or if it is a problem in my PoP
I also attach the results from 'aiccu autotest'
http://pastebin.ca/1577425
My Handle is AOZ3-SIXXS
and my Tunnel is T22807
Regards
-Andres
State change: confirmed
Jeroen Massar on Thursday, 24 September 2009 10:41:42
The state of this ticket has been changed to confirmed
Routing reaching most of the IPv6 internet
Jeroen Massar on Thursday, 24 September 2009 10:42:57
Looks like the London OCCAID node doesn't know where to route traffic, which results in packets not coming back to usqas01. OCCAID and Hotnic notified.
traceroute to usqas01.sixxs.net (2001:4830:e6:7::2) from 2001:838:1:1:210:dcff:fe20:7c7c, 30 hops max, 16 byte packets
1 ge-1-3-0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 0.361 ms 0.332 ms 0.329 ms
2 2001:838:5:a::1 (2001:838:5:a::1) 1.843 ms 1.809 ms 1.84 ms
3 nl-ams04a-re1-fe-0-0.ipv6.aorta.net (2001:7f8:1::a500:6830:1) 2.66 ms 2.57 ms 2.702 ms
4 at-vie01a-re1-t-2.ipv6.aorta.net (2001:730::1:21) 24.084 ms 23.971 ms 23.902 ms
5 de-fra02a-re1-t-2.ipv6.aorta.net (2001:730::1:45) 40.4 ms 40.308 ms 40.508 ms
6 fr-par02a-re1-t-2.ipv6.aorta.net (2001:730::1:2d) 51.669 ms 51.754 ms 51.521 ms
7 uk-lon01a-re1-t-1.ipv6.aorta.net (2001:730::1:2a) 94.687 ms 84.022 ms 83.754 ms
8 ibr01-ve26.lndn01.occaid.net (2001:7f8:4::7577:1) 116.347 ms !N 116.921 ms !N 116.522 ms !N
State change: resolved
Jeroen Massar on Friday, 25 September 2009 01:00:08
The state of this ticket has been changed to resolved
Routing reaching most of the IPv6 internet
Jeroen Massar on Friday, 25 September 2009 01:01:49
Ultimately it was a problem at Equinix where due to a too hasty emergency maintenance some VLANs where mis-configured. All should be back to normal again.
Posting is only allowed when you are logged in. |