SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1367093
Ticket Status: Remote Problem

PoP: nlams05 - SURFnet (Amsterdam)

Route problem to my teredo address
[nl] Shadow Hawkins on Saturday, 27 February 2010 19:52:52
I got a routing problem when using the surfnet POP, I cant reach from my teredo address "2001:0:53aa:64c:3871:3c7b:a7b1:924a" to my sixxs ipv6 "2001:610:600:66e::2". But I can reach them both from the shell server at XS4ALL. Here a traceroute from "2001:610:600:66e::2" (nl5ams) to my teredo address. This one failes. #traceroute6 2001:0:53aa:64c:3871:3c7b:a7b1:924a traceroute to 2001:0:53aa:64c:3871:3c7b:a7b1:924a (2001:0:53aa:64c:3871:3c7b:a7b1:924a) from 2001:610:600:66e::2, 30 hops max, 16 byte packets 1 gw-1647.ams-05.nl.sixxs.net (2001:610:600:66e::1) 1.722 ms 1.331 ms 1.134 ms 2 vl163.sw14.amsterdam1.surf.net (2001:610:1:80bb:192:87:102:97) 1.335 ms 1.331 ms 1.401 ms 3 2001:610:188:140:7268:7275:6c7a:4143 (2001:610:188:140:7268:7275:6c7a:4143) 1.589 ms 1.483 ms 1.468 ms 4 * * * 5 * * * 6 * * * ^C Here from "2001:610:600:66e::2" (nl5ams) to the shell server from xs4all. This one is ok. #traceroute6 xs6.xs4all.nl traceroute to xs6.xs4all.nl (2001:888:0:1::666) from 2001:610:600:66e::2, 30 hops max, 16 byte packets 1 gw-1647.ams-05.nl.sixxs.net (2001:610:600:66e::1) 1.639 ms 1.341 ms 1.332 ms 2 vl163.sw14.amsterdam1.surf.net (2001:610:1:80bb:192:87:102:97) 1.469 ms 1.259 ms 1.52 ms 3 2001:610:f01:9168::169 (2001:610:f01:9168::169) 1.581 ms 1.459 ms 1.556 ms 4 AE1.500.JNR02.Asd002A.surf.net (2001:610:e08:68::69) 1.766 ms 1.521 ms 1.607 ms 5 0.ge-0-2-0.xr1.sara.xs4all.net (2001:610:16:6056::58) 5.405 ms 2.193 ms 1.9 ms 6 0.so-2-0-0.xr4.1d12.xs4all.net (2001:888:0:1152::1) 9.374 ms 2.06 ms 2.036 ms 7 xs6.xs4all.nl (2001:888:0:1::666) 1.948 ms 2.047 ms 1.982 ms And here one from the shell server at xs4all to my teredo address. This one is also ok. #traceroute6 2001:0:53aa:64c:3871:3c7b:a7b1:924a traceroute6 to 2001:0:53aa:64c:3871:3c7b:a7b1:924a (2001:0:53aa:64c:3871:3c7b:a7b1:924a) from 2001:888:0:1::666, 30 hops max, 12 byte packets 1 124.ae0.xr4.1d12.xs4all.net 0.388 ms 0.312 ms 0.283 ms 2 0.ge-0-2-0.xr1.sara.xs4all.net 1.236 ms 29.506 ms 5.069 ms 3 ams-ix.ipv6.concepts.nl 0.767 ms 1.005 ms 0.956 ms 4 2001:838:5:a::2 2.650 ms 2.692 ms 2.614 ms 5 teredo-relay.concepts-ict.net 2.776 ms 2.524 ms 2.481 ms 6 2001:0:53aa:64c:3871:3c7b:a7b1:924a 27.294 ms 26.943 ms 26.182 ms So it seems the POP at surfnet doesn't know the route for my teredo address. Here are my tunnel details: My handle DK666-6BONE Tunnel Id : T25734 PoP Name : nlams05 (nl.surfnet [AS1103]) Your Location : Amsterdam, nl SixXS IPv6 : 2001:610:600:66e::1/64 Your IPv6 : 2001:610:600:66e::2/64 SixXS IPv4 : 192.87.102.107 Tunnel Type : Static (Proto-41) Your IPv4 : 213.19.146.50
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 28 February 2010 21:09:26
Message is Locked
The state of this ticket has been changed to remoteproblem
Route problem to my teredo address
[ch] Jeroen Massar SixXS Staff on Sunday, 28 February 2010 21:13:16
Like 6to4, Teredo is a mess to debug as one needs access to every single router in the path for both IPv4 and IPv6, otherwise you do not know where the packets are truly going to. Teredo and 6to4 happen somewhere remotely on the Internet, we do not have control over it and thus it is extremely hard to find where it goes wrong and thus fix, sorry :(

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker