|
No route to tunnels on decgn01
![[de]](/s/countries/de.gif) Shadow Hawkins on Monday, 05 September 2011 14:49:51
Hi everyone,
I just set up my second IPv6 tunnel.
This time, I tried to connect a Fritz!Box using the heartbeat protocol.
On the Fritz!Box, I got the proper configuration and the box reports no problems.
Unfortunately, I can't get a ping to the tunnel's endpoint.
This is the output of the tracert program (in german):
Routenverfolgung zu 2001:4dd0:ff00:8b53::1 ber maximal 30 Abschnitte
1 14 ms 10 ms 10 ms gw-1500.dus-01.de.sixxs.net [2a01:198:200:5db::1]
2 10 ms 10 ms 10 ms sixxs-dus.dus.speedpartner.de [2a01:198:200::1]
3 11 ms 11 ms 11 ms 2001:7f8:8::20e6:0:1
4 11 ms 11 ms 11 ms core-pg2-te1-3.netcologne.de [2001:4dd0:a2b:9:dc10::c]
5 12 ms 11 ms 11 ms core-eup2-te4-2.netcologne.de [2001:4dd0:a2b:1f:dc40::1]
6 11 ms 11 ms 11 ms 2001:4dd0:1234:3::42
7 11 ms 11 ms 11 ms gw-2579.cgn-01.de.sixxs.net [2001:4dd0:ff00:a12::1]
8 Zielnetz nicht erreichbar.
Ablaufverfolgung beendet.
<<< EOF
In english: The traceroute stops at the 8th hop because of "No route".
You can get the same results when trying to ping arbitrary tunnel endpoints from different users on decgn01.
Is this a problem on the POP, or could someone help me find the problem?
Best regards
Daniel
No route to tunnels on decgn01
You can get the same results when trying to ping arbitrary tunnel endpoints from different users on decgn01.
Tunnels which are not configured get a endpoint unreachable as there won't be any route there either.
If you are not sending proper heartbeats then you your tunnel won't be configured either.
My traceroute ends in:
5 2001:4dd0:1234:3::42 (2001:4dd0:1234:3::42) 6.024 ms 5.997 ms 5.991 ms
6 gw-2900.cgn-01.de.sixxs.net (2001:4dd0:ff00:b53::1) 5.963 ms 5.998 ms 6.211 ms
7 cl-2900.cgn-01.de.sixxs.net (2001:4dd0:ff00:b53::2) 20.542 ms !X 21.615 ms !X 24.274 ms !X
I am quite a bit surprised about your hop 7 though, as that looks totally out of place.
Greets,
Jeroen
No route to tunnels on decgn01
Shadow Hawkins on Monday, 05 September 2011 15:18:37> You can get the same results when trying to ping arbitrary tunnel endpoints from different users on decgn01.
Tunnels which are not configured get a endpoint unreachable as there won't be any route there either.
My tunnel seems to be configured properly, the website says:
Created2011-09-05 13:38:19 CEST
Last Alive2011-09-05 15:02:57 CEST
7 cl-2900.cgn-01.de.sixxs.net (2001:4dd0:ff00:b53::2) 20.542 ms !X 21.615 ms !X 24.274 ms !X
It's not surprising that the endpoint does not respond to ICMP ping, that's the default setting for Fritz!Boxes..
6 gw-2900.cgn-01.de.sixxs.net (2001:4dd0:ff00:b53::1) 5.963 ms 5.998 ms 6.211 ms
I am quite amazed, that you are able to ping the endpoint on the POP side.
My traceroute (which was performed on sixxs-enabled host on dedus01) ends different than yours.
Even more surprising, running the traceroute from another host (http://www.subnetonline.com/pages/ipv6-network-tools/online-ipv6-traceroute.php), yields the same results as yours:
traceroute to 2001:4dd0:ff00:b53::2 (2001:4dd0:ff00:b53::2), 30 hops max, 40 byte packets
1 2001:1af8:4200:b000::1 (2001:1af8:4200:b000::1) 1.207 ms 1.238 ms 1.316 ms
2 2001:1af8:4100::5 (2001:1af8:4100::5) 1.100 ms 1.151 ms 1.217 ms
3 be11.crs.evo.leaseweb.net (2001:1af8::9) 2.188 ms 2.175 ms 2.160 ms
4 rtamsix-te31.netcologne.de (2001:7f8:1::a500:8422:1) 1.789 ms 2.035 ms 1.947 ms
5 core-eup2-vl31.netcologne.de (2001:4dd0:a2b:6d:dc40::c2) 5.730 ms 5.642 ms 5.528 ms
6 2001:4dd0:1234:3::42 (2001:4dd0:1234:3::42) 5.253 ms 4.992 ms 4.993 ms
7 gw-2900.cgn-01.de.sixxs.net (2001:4dd0:ff00:b53::1) 5.133 ms 4.963 ms 4.945 ms
8 cl-2900.cgn-01.de.sixxs.net (2001:4dd0:ff00:b53::2) 26.604 ms !X 21.062 ms !X 21.284 ms !X)
No route to tunnels on decgn01
Shadow Hawkins on Monday, 05 September 2011 15:20:29
Okay, the problem seems to be resolved.
Running the same traceroute from the same host again, yields the correct results:
Routenverfolgung zu 2001:4dd0:ff00:8b53::2 ber maximal 30 Abschnitte
1 15 ms 10 ms 10 ms gw-1500.dus-01.de.sixxs.net [2a01:198:200:5db::1]
2 10 ms 10 ms 10 ms sixxs-dus.dus.speedpartner.de [2a01:198:200::1]
3 11 ms 11 ms 11 ms 2001:7f8:8::20e6:0:1
4 12 ms 11 ms 11 ms core-pg1-te1-3.netcologne.de [2001:4dd0:a2b:8:dc10::c]
5 11 ms 11 ms 13 ms core-eup2-te4-1.netcologne.de [2001:4dd0:a2b:1d:dc40::1]
6 11 ms 11 ms 11 ms 2001:4dd0:1234:3::42
7 11 ms 11 ms 11 ms gw-2900.cgn-01.de.sixxs.net [2001:4dd0:ff00:b53::1]
8 Zielnetz nicht erreichbar.
Ablaufverfolgung beendet.
Idk why the traceroute was messed up in the beginning..
|
![[ch]](/s/countries/ch.gif)
on Monday, 05 September 2011 15:06:53
Posting is only allowed when you are