SixXS vs. 6to4
jeroen at unfix.org
Sat Dec 31 05:08:14 CET 2011
On 2011-12-31 04:47 , Ivan Shmakov wrote:
> It looks like there's a connectivity problem in between the
> SixXS.net and 6to4 worlds.
You actually mean "between the SixXS AMIS PoP and 6to4", there are quite
a few networks involved in "SixXS".
> Please consider, e. g.:
> $ traceroute6 -s 2002:bc78:XXXX::1 \
Without a full IP address those traceroutes are completely useless.
> traceroute to 2001:15c0:XXXX::1 (2001:15c0:XXXX::1) from 2002:bc78:XXXX::1, port 33434, from port 50121, 30 hops max, 60 byte packets
> 1 * * *
> 5 * * *
> 6 maribor3-te-7-4.amis.net (2001:15c0:ffff:d::d) 146.467 ms 170.284 ms 135.588 ms
> 7 * * *
> 29 * * *
> 30 * * *
Looks like a lot of packets are lost on some magical links somewhere in
the wild wild Internet.
6to4 is this funny anycasted in IPv4 and IPv6 thing. Lots of Magic there.
I suggest you provide full IPv6 addresses and use for instance
http://www.sixxs.net/tools/traceroute/ for figuring out more about the
various paths it might be taking.
> The same destination is reachable via a HE.net 6in4 tunnel from
> the same host, like:
> $ traceroute6 -s 2001:470:XXXX::1 \
Please look up the big difference between 6to4 and 6in4 and other kinds
of configured tunnels.
> traceroute to 2001:15c0:XXXX::1 (2001:15c0:XXXX::1) from 2001:470:XXXX::1, port 33434, from port 50092, 30 hops max, 60 byte packets
> 1 * * *
> 5 * * *
Are you firewalling that all those hops are missing?
Don't expect a lot of folks to care about 6to4 around this time of year
though, but maybe you are lucky and some 6to4-debugger might help you
out, but you will need to provide full addresses...
A quick fix: use real tunnels, ignore that 6to4 mess.
Maybe 2012 could be the year that 2002::/16 gets disabled like 2006 was
the year that the 6bone died?
More information about the ipv6-ops