SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #407872
Ticket Status: Resolved

PoP: fihel01 - DNA Oy (Helsinki)

Unable to reach 6to4 ipv6 addresses
[fi] Shadow Hawkins on Sunday, 17 September 2006 21:09:30
Hello. I'm using sixxs tunnel number T9520 by user TLG1-SIXXS. My ipv6 address is 2001:14b8:100:18e::2 and ipv4 213.139.187.253. Tunnels work fine for all other ipv6 addresses, except 6to4. I ran 'aiccu test' and there were no problems. My system is 'Linux porogrammer 2.6.16-1-686 #2 Thu May 4 18:22:23 UTC 2006 i686 GNU/Linux' (Debian unstable). When trying to contact some 6to4 -type ipv6 address from my system, traceroute6 shows following: user@porogrammer:~$ traceroute6 papu.6dns.org traceroute to papu.6dns.org (2002:d432:868a::1) from 2001:14b8:100:18e::2, 30 hops max, 16 byte packets 1 gw-399.hel-01.fi.sixxs.net (2001:14b8:100:18e::1) 11.627 ms 11.386 ms 11.511 ms 2 van5r3.ip6.fv.fi (2001:14b8:0:2000::201) 11.915 ms 11.837 ms 11.796 ms 3 hki1r5.ip6.fv.fi (2001:14b8::4) 12.274 ms 12.464 ms 12.371 ms 4 song.ficix2-ge.ficix.fi (2001:7f8:7:1::3246:1) 12.766 ms 12.394 ms 12.378 ms 5 psl-p2.hel.fi.6.sn.net (2001:6e8:1:1:1:1:2:3) 12.824 ms 12.322 ms 12.564 ms 6 ltt-p2.hel.fi.6.sn.net (2001:6e8:1:1:1:1:1:5) 12.784 ms 12.63 ms 12.475 ms 7 * * * 8 ltt-ipv6-pe1.hel.fi.6.sn.net (2001:6e8:1:1:1:1:1:2) 13.636 ms 12.941 ms 13.394 ms 9 * * * 10 * * * 11 * * * 12 * * * And when trying to connect from the other end to my machine, traceroute6 shows: user@papu:~ $ traceroute6 porogrammer.org traceroute to porogrammer.org (2001:14b8:100:18e::2), 30 hops max, 40 byte packets 1 2002:c058:6301::1741 (2002:c058:6301::1741) 12.444 ms 12.905 ms 12.680 ms 2 csc0-g4100-sixpack.ipv6.funet.fi (2001:708:0:1::625) 12.921 ms 21.999 ms 22.120 ms 3 finnet.ficix1-ge.ficix.fi (2001:7f8:7::1:6086:1) 13.569 ms 12.955 ms 12.752 ms 4 * * * 5 * * * 6 * * * 7 * * * Is there any possibilities to fix this? You can contact me for more information by email to <removed> Thanks.
State change: wontfix Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 12 August 2006 14:43:11
Message is Locked
The state of this ticket has been changed to wontfix
Unable to reach 6to4 ipv6 addresses
[ch] Jeroen Massar SixXS Staff on Saturday, 12 August 2006 14:44:16
6to4 is one of those nice 'technologies' which are totally impossible to debug. It is absolutely unknown what and where traffic flows to or where it breaks. Sorry but can't help you out here.
Unable to reach 6to4 ipv6 addresses
[de] Shadow Hawkins on Sunday, 13 August 2006 00:18:23
Hi Timo, the 6to4 setup at papu.6dns.org is probably broken, I can reach it when coming through a 6to4 relay which uses 192.88.99.1 (the anycast IP) as source address, but it is broken when the relay uses its unicast IP as source. I guess the one you are using from fihel01 (the one at Song) uses its unicast address as well. The 6to4 client must not check or rely on a specific source address, which means the tunnel has to be "remote any" and stateful firewalling for proto 41 has to be disabled. Regards, Bernhard
Unable to reach 6to4 ipv6 addresses
[fi] Shadow Hawkins on Monday, 14 August 2006 08:36:35
Fixed, Thanks to Bernhard. --Timo
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Monday, 11 September 2006 13:07:10
Message is Locked
The state of this ticket has been changed to resolved

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

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