SixXS vs. 6to4

[Meftah Tayeb]

cd /internet/ipv6
rm -Rf sixxs
cd he.net
mkdir tunnel1.he.net
:)

----- Original Message ----- 
From: "Ivan Shmakov" <oneingray at gmail.com>
To: <ipv6-ops at lists.cluenet.de>
Sent: Saturday, December 31, 2011 5:47 AM
Subject: SixXS vs. 6to4


> It looks like there's a connectivity problem in between the
> SixXS.net and 6to4 worlds.  Please consider, e. g.:
>
> $ traceroute6 -s 2002:bc78:XXXX::1 \
>      2001:15c0:XXXX::1
> 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  * * *
> $
>
> The same destination is reachable via a HE.net 6in4 tunnel from
> the same host, like:
>
> $ traceroute6 -s 2001:470:XXXX::1 \
>      2001:15c0:XXXX::1
> 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  * * *
> 6  maribor3-te-7-4.amis.net (2001:15c0:ffff:d::d)  147.248 ms  171.618 ms 
> 215.410 ms
> 7  simbx01.sixxs.net (2001:15c0:ffff:7::2)  171.574 ms  143.399 ms 
> 141.565 ms
> 8  2001:15c0:XXXX::1 (2001:15c0:XXXX::1)  287.687 ms  325.801 ms  268.182 
> ms
> $
>
> As the traceroutes above start to differ at the link between
> 2001:15c0:ffff:d::d and 2001:15c0:ffff:7::2, I'd assume that one
> of these is in charge.
>
> TIA.  And HNY.
>
> -- 
> FSF associate member #7257
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus 
> signature database 6756 (20111230) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> 


__________ Information from ESET NOD32 Antivirus, version of virus signature database 6756 (20111230) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com