|
Strange things between SixXS and 6to4
![[de]](/s/countries/de.gif) Shadow Hawkins on Thursday, 03 March 2011 01:17:31
Hi,
I have two servers and a laptop.
One of the servers has an own IPv6 (2001:...),
the other has a 6to4 tunnel (should be fine, as the IPv4 is static),
and I have now setup SixXS on my laptop.
The strange thing is: Connection between the servers as well as between the laptop and server 1 is fine via IPv6.
But when I try to reach server 2, the 6to4 one, the connection stucks and eventually times out.
Huh? What tells me that?
* Laptop/SixxS should be fine, as I can reach server 1 as well as other IPv6 sites.
* Server 2 is fine, as it can reach server 1 and other sites.
But they don't talk with each other. Why not? Ideas, anyone?
TIA
Strange things between SixXS and 6to4
one word: traceroutes
or the actual question: where are the traceroutes.
Do realize that 6to4 is anycast on both IPv4 and IPv6 and that it is quite hard to debug and there are a lot of pitfalls and misconfigurations.
Also note that stating 'SiXXs and 6to4' is always wrong as the PoPs use space by the ISPs whom each have their own routing policies.
Strange things between SixXS and 6to4
Shadow Hawkins on Friday, 04 March 2011 08:26:28
Thanks for your answer. Here are the missing traceroutes:
From me towards the 6to4 server:
1 XXX 32.061 ms 32.209 ms 33.256 ms
2 2001:4dd0:1234:3:dc40::a (2001:4dd0:1234:3:dc40::a) 32.887 ms 32.245 ms 32.810 ms
3 2001:4dd0:a2b:21:dc30::1 (2001:4dd0:a2b:21:dc30::1) 34.026 ms 34.540 ms 2001:4dd0:a2b:23:dc30::1 (2001:4dd0:a2b:23:dc30::1) 35.455 ms
4 2001:4dd0:a2b:17:dc30::a (2001:4dd0:a2b:17:dc30::a) 36.322 ms 2001:4dd0:a2b:1:dc30::a (2001:4dd0:a2b:1:dc30::a) 37.193 ms 37.821 ms
5 * * *
6 * * *
...
From me towards the working OVH server:
traceroute to XXX, 30 hops max, 40 byte packets using UDP
1 XXX 32.169 ms 32.081 ms 33.132 ms
2 2001:4dd0:1234:3:dc40::a (2001:4dd0:1234:3:dc40::a) 33.492 ms 33.409 ms 34.029 ms
3 2001:4dd0:a2b:6d:30::b (2001:4dd0:a2b:6d:30::b) 39.967 ms 39.677 ms 40.204 ms
4 amsix2.routers.ovh.net (2001:7f8:1::a501:6276:2) 50.104 ms 50.115 ms *
5 rbx-g2-a9.fr.eu (2001:41d0::ac1) 52.447 ms 54.445 ms 53.538 ms
6 rbx-2-6k.fr.eu (2001:41d0::6b2) 53.435 ms * *
7 th2-1-6k.fr.eu (2001:41d0::5b1) 43.925 ms * *
8 p19-2-6k.fr.eu (2001:41d0::512) 45.417 ms * *
9 2001:41d0:1:22b::1 (2001:41d0:1:22b::1) 44.908 ms 44.109 ms 45.989 ms
From OVH to the 6to4 (for completeness):
1 p19-2-6k.fr.eu (2001:41d0:1:2ff:ff:ff:ff:ff) 0.307 ms * *
2 p19-7-6k.fr.eu (2001:41d0::561) 0.337 ms * *
3 th1-1-6k.fr.eu (2001:41d0::5d2) 0.435 ms * *
4 fra-5-6k.de.eu (2001:41d0::b91) 9.188 ms * *
5 zr-fra1-te0-0-0-3.x-win.dfn.de (2001:7f8::2a8:0:1) 10.556 ms 10.212 ms 10.093 ms
6 zr-erl1-te0-7-0-2.x-win.dfn.de (2001:638:c:c04a::1) 24.123 ms 23.732 ms 23.769 ms
7 xr-erl1-te2-1.x-win.dfn.de (2001:638:c:c049::1) 22.884 ms 22.960 ms 22.973 ms
8 2002:XXX 27.724 ms 27.727 ms 27.789 ms
From 6to4 to my laptop:
1 2002:XXX 1.257 ms 1.256 ms 1.278 ms
2 gige-g2-6.core1.fra1.he.net (2001:470:0:150::1) 1.172 ms 1.334 ms 1.176 ms
3 * * *
4 * * *
[...]
From 6to4 to OVH (for completeness):
traceroute to r03 (2001:41d0:1:22b::1), 30 hops max, 40 byte packets
1 2002:XXX 0.690 ms 0.899 ms 0.997 ms
2 gige-g2-6.core1.fra1.he.net (2001:470:0:150::1) 1.195 ms 0.881 ms 1.104 ms
3 decix.routers.ovh.net (2001:7f8::3f94:0:1) 18.694 ms 18.361 ms *
4 th1-1-6k.fr.eu (2001:41d0::b92) 27.733 ms * *
5 p19-7-6k.fr.eu (2001:41d0::5d1) 27.497 ms * *
6 p19-2-6k.fr.eu (2001:41d0::562) 27.650 ms * *
7 XXX 27.422 ms 27.030 ms 27.478 ms
Strange things between SixXS and 6to4
If you want anybody to help you with this at all, then hiding source/destination addresses is not going to help at all and nobody, if there is somebody who actually cares about 6to4, will be able to help you.
My best advice though in the case of 6to4 is to stop using it and just get an AYIYA tunnel (in case of being behind a NAT) or a 6in4-heartbeat tunnel in case you get a public address.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 03 March 2011 09:56:34
Posting is only allowed when you are