The route between the HE Paris tunnel endpoint (2001:470::/32) and 2001:41d0::/32 (OVH, AS16276) seems broken. Sample output from the looking glass:
core1.par1.he.net> traceroute ipv6 2001:41d0::16e
Sending DNS Query to 216.218.252.93
Tracing the route to IPv6 node gsw-g1-a9.fr.eu(2001:41d0::16e)from 1 to 30 hops
1 8 ms <1 ms <1 ms 10gigabitethernet1-1.core1.par2.he.net [2001:470:0:1b0::2]
2 <1 ms 45 ms 40 ms gin-pvu-icore1.as6453.net [2001:7f8:43::6453:1]
3 9 ms 1 ms 1 ms if-ae2.2.tcore1.PVU-Paris.ipv6.as6453.net [2a01:3e0:fff0:400::d]
4 * * * ?
5 * * * ?
6 * * * ?
7 * * * ?
IP: Errno(8) Trace Route Failed, no response from target node.
# Entry cached for another 31 seconds.
core1.fmt1.he.net> traceroute ipv6 2001:41d0::16e
Tracing the route to IPv6 node 2001:41d0::16e from 1 to 30 hops
1 6 ms <1 ms <1 ms 2001:470:0:2f::2
2 <1 ms <1 ms 12 ms 2001:2000:3080:1b7::1
3 140 ms 117 ms 116 ms 2001:2000:3018:30::1
4 * * * ?
5 * * * ?
6 * * * ?
7 * * * ?
IP: Errno(8) Trace Route Failed, no response from target node.
# Entry cached for another 6 seconds.
Is there some place one can (should) report this sort of things?
I don't grok BGP, so I don't know how to analyze the problem and determine who's at fault.
(This route is terribly important to me because my home PC's are use the HE tunnel in question and one of my servers is hosted by OVH.)
Ipv6@he.net
I tested traceroute to 2001:41d0::16e through two different tunnel brokers, native IPv6, and 6to4. I did not get a reply from 2001:41d0::16e using any of those four methods.
It's still down, don't know who's at fault here, but in the HE.net end you can see that it's not working in the BGP Status:
http://ipv6.he.net/bgpview/bgp.html (http://ipv6.he.net/bgpview/bgp.html) -> http://ipv6.he.net/bgpview/200x-stability.html (http://ipv6.he.net/bgpview/200x-stability.html) -> http://ipv6.he.net/bgpview/24h_history/FR-OVH-20041115.html (http://ipv6.he.net/bgpview/24h_history/FR-OVH-20041115.html)
I also have one he.net tunnel at home and one server at ovh in france, I can ping6 google, bing, kame.net at home and from the server in ovh, but I can't ping between home and server in either way.
This thread is probably related to this one : http://www.tunnelbroker.net/forums/index.php?topic=2823.0
One more example : I can't access www.freenews.fr which is also on OVH.
I just tested from freenet6 and bytemark
freenet6:
traceroute to 2001:41d0::16e (2001:41d0::16e), 30 hops max, 80 byte packets
1 2001:5c0:1400:a::350 (2001:5c0:1400:a::350) 24.882 ms 30.845 ms 30.948 ms
2 ve8.ipv6.colo-rx4.eweka.nl (2001:4de0:1000:a22::1) 31.076 ms 31.151 ms 31.228 ms
3 9-1.ipv6.r2.am.hwng.net (2001:4de0:a::1) 40.663 ms 40.769 ms 40.869 ms
4 * * *
bytemark:
traceroute to 2001:41d0::16e (2001:41d0::16e), 30 hops max, 80 byte packets
1 gateway.vlan855.bytemark.co.uk (2001:41c8:10:200::1) 0.509 ms 0.494 ms 0.500 ms
2 2001:41c8:0:104::1 (2001:41c8:0:104::1) 0.469 ms 0.474 ms 0.655 ms
3 te-8-1.car1.Manchester1.Level3.net (2001:1900:5:2:2::136d) 0.457 ms 0.455 ms 0.632 ms
4 vl-4062.edge4.London1.Level3.net (2001:1900:5:1::241) 6.304 ms 6.304 ms 6.296 ms
5 vl-4081.edge3.London1.Level3.net (2001:1900:5:1::105) 6.454 ms vl-4080.edge3.London1.Level3.net (2001:1900:5:1::101) 6.443 ms vl-4081.edge3.London1.Level3.net (2001:1900:5:1::105) 6.438 ms
6 * * *
From looking at these traces and from the BGP stuff redvip linked it seems pretty clear to me that the problem is on ovh's end. I would suggest telling them to fix their IPv6 connectivity and if they fail to do so in a reasonable time to stop doing buisness with them.
I think problem is on OVH side, since I can not reach your destination also.
Quote
E:\>tracert 2001:41d0::16e
Tracing route to gsw-g1-a9.fr.eu [2001:41d0::16e]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms gw-8000.s04.ipv6.tnc92.net [2400:8900:efff:8000:
:1]
2 <1 ms <1 ms <1 ms ge-5.r01-pnh.tnc92.net [2400:8900:efff:2001::1]
3 105 ms 105 ms 105 ms r01-tyo.p2p-3013.s04.ipv6.tnc92.net [2400:8900:e
fff:3013::2]
4 105 ms 105 ms 106 ms 2400:8900:ffff:0:4255:39ff:fea7:57bf
5 107 ms 105 ms 105 ms 2001:268:f702:6c::1
6 131 ms 107 ms 106 ms 6otejbb206.int-gw.kddi.ne.jp [2001:268:fb13:2::1
]
7 205 ms 207 ms 206 ms 6pajbb002.int-gw.kddi.ne.jp [2001:268:fb02:55::2
]
8 224 ms 218 ms 212 ms 6ix-pa7.int-gw.kddi.ne.jp [2001:268:fb81:4::2]
9 246 ms 212 ms 212 ms kddi.paloalto2.pao.seabone.net [2001:41a8:4060:2
::25]
10 300 ms 289 ms 289 ms mia15-loop0-v6.mia.seabone.net [2001:41a8:4020::
f]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 ^C
E:\>
This should be cleared up now. Go ahead and test things again.
Still seems broken according to the he looking glass and according to my own traceroutes from freenet6 and bytemark.
Quote from: plugwash on March 19, 2013, 10:25:02 AMStill seems broken
Did 2001:41d0::16e ever respond? Look at a traceroute to a functional IP address in that network.
traceroute to ipv6-test.com (2001:41d0:1:d87c::7e57:1), 30 hops max, 80 byte packets
1 2a01:d0:839a:babe:735d:77a7:990d:702c 0.099 ms 0.113 ms 0.140 ms
2 2a01:d0:ffff:39a::1 63.639 ms 65.097 ms 67.204 ms
3 2a01:d0:0:1c::19 66.002 ms 64.358 ms 64.391 ms
4 2001:470:1:70::1 101.647 ms 101.694 ms 100.798 ms
5 2001:470:0:168::2 141.828 ms 140.708 ms 140.732 ms
6 2001:2000:3018:18::1 125.489 ms 125.534 ms 125.531 ms
7 * * *
8 2001:41d0::c32 211.142 ms 211.792 ms 211.795 ms
9 2001:41d0::731 211.818 ms * *
10 2001:41d0::5a1 171.366 ms 171.389 ms 172.004 ms
11 2001:41d0::b71 170.711 ms 125.299 ms 125.309 ms
12 2001:41d0::aa2 125.646 ms * *
13 * 2001:41d0:1:d87c::7e57:1 104.438 ms 122.608 ms
On the route I see multiple replies from 2001:41d0::/112. But if I try to do a traceroute to any of those addresses I get no reply past the border of that network. It can't be just the router not responding to echo request, as I don't see replies from the earlier routers either.
traceroute to 2001:41d0::aa2 (2001:41d0::aa2), 30 hops max, 80 byte packets
1 2a01:d0:839a:babe:735d:77a7:990d:702c 0.134 ms 0.113 ms 0.137 ms
2 2a01:d0:ffff:39a::1 76.237 ms 77.910 ms 80.864 ms
3 2a01:d0:0:1c::19 80.237 ms 60.822 ms 61.170 ms
4 2001:470:1:70::1 90.623 ms 91.253 ms 88.949 ms
5 2001:470:0:168::2 121.664 ms 121.495 ms 121.528 ms
6 2001:2000:3018:18::1 124.930 ms 124.224 ms 124.238 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Either they have some weird filter on the border of their network. Or they simply don't have a working route to 2001:41d0::/112, but use it as source address for ICMPv6 errors anyway.
So far I haven't heard anything back from OVH in their forums http://foros.ovh.es/showthread.php?t=10826 (http://foros.ovh.es/showthread.php?t=10826) (in spanish as I'm a spanish customer)
In the OVH BGP status (http://ipv6.he.net/bgpview/24h_history/FR-OVH-20041115.html (http://ipv6.he.net/bgpview/24h_history/FR-OVH-20041115.html)) is still marked as not working, but I can ping and access my server from home and viceversa:
traceroute -6 -I -A noticias.juridicas.com
traceroute to noticias.juridicas.com (2001:41d0:2:f1ca::2), 30 hops max, 80 byte packets
1 2001:470:1f13:5bd::1 (2001:470:1f13:5bd::1) [AS6939] 0.439 ms 1.374 ms 0.416 ms
2 redvip-1.tunnel.tserv10.par1.ipv6.he.net (2001:470:1f12:5bd::1) [AS6939] 84.667 ms 77.440 ms 83.475 ms
3 gige-g2-3.core1.par1.he.net (2001:470:0:7b::1) [AS6939] 69.441 ms 80.180 ms 75.516 ms
4 10gigabitethernet1-1.core1.par2.he.net (2001:470:0:1b0::2) [AS6939] 78.030 ms 69.373 ms 76.836 ms
5 gin-pvu-icore1.as6453.net (2001:7f8:43::6453:1) [AS44729] 77.714 ms 76.967 ms 70.432 ms
6 if-ae12.2.tcore1.PVU-Paris.ipv6.as6453.net (2a01:3e0:fff0:400::46) [AS6453] 76.496 ms 81.910 ms 67.660 ms
7 * 2a01:3e0:ff80:100::36 (2a01:3e0:ff80:100::36) [AS6453] 113.589 ms *
8 gsw-g1-a9.fr.eu (2001:41d0::16e) [AS16276] 75.533 ms * *
9 rbx-g2-a9.fr.eu (2001:41d0::16b) [AS16276] 101.266 ms 92.068 ms 95.515 ms
10 vss-8b-6k.fr.eu (2001:41d0::173) [AS16276] 88.103 ms 96.249 ms 82.384 ms
11 2001:41d0:2:f1ca::2 (2001:41d0:2:f1ca::2) [AS16276] 83.065 ms 99.247 ms 94.131 ms
As it's not posted here I will paste the answer I received from ipv6@he.net:
Quote
OVH is apparently trying to route traffic to us over an exchange where
we do not peer, and as such, the traffic is being dropped at our border.
If this issue persists, you can contact OVH if you are their customer.