I have a similar problem. From my he.net tunnel to Stockholm pop I cannot get to AS39326.
$ traceroute6 -Il ns3.mattsk.se
traceroute6 to ns3.mattsk.se (2a01:348:48::53) from 2001:470:dc9b::53, 64 hops max, 16 byte packets
1 2001:470:dc9b::1 (2001:470:dc9b::1) 0.576 ms 0.514 ms 0.41 ms
2 mattsk-1.tunnel.tserv24.sto1.ipv6.he.net (2001:470:27:2cf::1) 13.439 ms 11.584 ms 8.238 ms
3 gige-g2-20.core1.sto1.he.net (2001:470:0:11e::1) 15.118 ms 9.817 ms 12.713 ms
4 * * *
5 * * *
Tested using my tunnels to Amsterdam and Frankfurt.
ns3.mattsk.se - works.
www.nte.no - do not works, packets are droped as they enter HE backbone.
It looks like this issue is a route filtering somwhere between Cogent and HE.
i'll send an email to AS-NTE (34087) to see id they could help me.. :)
mattsk.se is not the same issue as routing to AS39326 exists in the routing table..
so maby creatinga another topic with this issue?
Quote from: runborg on February 07, 2011, 10:34:29 PM
It looks like this issue is a route filtering somwhere between Cogent and HE.
i'll send an email to AS-NTE (34087) to see id they could help me.. :)
mattsk.se is not the same issue as routing to AS39326 exists in the routing table..
so maby creatinga another topic with this issue?
the only thing in between HE and Cogent is a peering dispute. There is no filter, there is just no way to get from AS174 to AS6939 (assuming this is really your problem).
http://en.wikipedia.org/wiki/Comparison_of_IPv6_support_by_major_transit_providers
I have AS174 native IPv6 connectivity and I cannot get to www.nte.no either;
v6#traceroute www.nte.no
Type escape sequence to abort.
Tracing the route to www.nte.no (2A01:560:300:200::2)
1 2001:550:2:16::9 [AS 174] 4 msec 120 msec 4 msec
2 ::FFFF:154.54.0.37 104 msec 104 msec
::FFFF:154.54.0.13 104 msec
3 ::FFFF:154.54.0.73 108 msec
::FFFF:154.54.26.142 108 msec
::FFFF:130.117.0.254 108 msec
4 ::FFFF:154.54.37.129 108 msec
::FFFF:154.54.37.109 104 msec
::FFFF:154.54.37.77 104 msec
5 ::FFFF:130.117.50.46 104 msec
::FFFF:130.117.50.38 108 msec
::FFFF:130.117.50.54 108 msec
6 2001:978:2:30::1 [AS 174] 108 msec 104 msec 104 msec
7 2001:978:2:30::6 [AS 174] 104 msec
::FFFF:130.117.50.46 108 msec
2001:978:2:30::6 108 msec
8 2A01:560:200:3::2 [AS 34087] 116 msec 116 msec 116 msec
9 2A01:560:200:3::1 [AS 34087] 116 msec 112 msec 116 msec
10 2A01:560:200:3::2 [AS 34087] 116 msec 112 msec 112 msec
11 2A01:560:200:3::1 [AS 34087] 112 msec 116 msec 112 msec
12 2A01:560:200:3::2 [AS 34087] 116 msec 116 msec 112 msec
13 2A01:560:200:3::1 [AS 34087] 112 msec 116 msec 116 msec
14 2A01:560:200:3::2 [AS 34087] 116 msec 116 msec 116 msec
15 2A01:560:200:3::1 [AS 34087] 120 msec 116 msec 116 msec
16 2A01:560:200:3::2 [AS 34087] 116 msec 112 msec 116 msec
17 2A01:560:200:3::1 [AS 34087] 116 msec 116 msec 116 msec
18 2A01:560:200:3::2 [AS 34087] 116 msec 116 msec 116 msec
19 2A01:560:200:3::1 [AS 34087] 116 msec 116 msec 116 msec
20 2A01:560:200:3::2 [AS 34087] 116 msec 112 msec 112 msec
21 2A01:560:200:3::1 [AS 34087] 112 msec 116 msec 116 msec
22 2A01:560:200:3::2 [AS 34087] 112 msec 116 msec 116 msec
23 2A01:560:200:3::1 [AS 34087] 116 msec
2A01:560:200:3::2 116 msec
2A01:560:200:3::1 116 msec
24 2A01:560:200:3::2 [AS 34087] 116 msec 116 msec 116 msec
25 2A01:560:200:3::1 [AS 34087] 124 msec 116 msec 116 msec
26 2A01:560:200:3::2 [AS 34087] 116 msec 116 msec 116 msec
27 2A01:560:200:3::1 [AS 34087] 120 msec 116 msec 116 msec
28 2A01:560:200:3::2 [AS 34087] 116 msec 116 msec 116 msec
29 2A01:560:200:3::1 [AS 34087] 120 msec 116 msec 120 msec
30 2A01:560:200:3::2 [AS 34087] 116 msec 116 msec 116 msec
Destination not found inside max hopcount diameter.
Hi Runar.
Thanks for your report, the issue reached me through our CS, and we're looking into this now. As far as I can tell, Cogent is not announcing correctly. We're looking into this, but I can't guarantee we'll get this sorted before after the weekend.
-Edit: Nope, can't blame Cogent this time. It was actually inside our network, and of a nature that doesn't allow us to fix this until sunday night. I hope you can bear with us until then.
Best regards,
Kenneth Aalberg
NTE Broadband