|
Ticket ID: SIXXS #1363258 Ticket Status: Remote Problem PoP: simbx01 - Amis (Maribor)
6to4 broken on simbx01
![[cz]](/s/countries/cz.gif) Shadow Hawkins on Sunday, 21 February 2010 00:22:31
Hi, I recently noticed that outgoing 6to4 is broken on one of my tunnels:
== cut ==
[fis@graybox ~]$ ping6 -c 5 pasky.or.cz
PING pasky.or.cz(pasky.or.cz) 56 data bytes
--- pasky.or.cz ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms
[fis@graybox ~]$ /usr/sbin/traceroute6 pasky.or.cz
traceroute to pasky.or.cz (2002:3e18:58f1::) from 2001:15c0:670c:e3a7:224:1dff:fed0:f786, 30 hops max, 24 byte packets
1 nareem.teonas (2001:15c0:670c:e3a7:20e:2eff:fe39:6d4c) 0.367 ms 0.272 ms 0.227 ms
2 gw-376.mbx-01.si.sixxs.net (2001:15c0:65ff:177::1) 41.766 ms 40.915 ms 41.482 ms
3 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 47.096 ms 41.006 ms 41.064 ms
4 * * *
...
== cut ==
Meanwhile, from different location outside of sixxs, this works. This also works from another location under my control that has tunnel to deham01 PoP, so it's apparently not sixxs-wide problem, but it is somehow related to the PoP in question.
State change: confirmed
 ![[de]](/s/countries/de.gif) Shadow Hawkins on Monday, 22 February 2010 00:52:12
The state of this ticket has been changed to confirmed
State change: remoteproblem
The state of this ticket has been changed to remoteproblem
6to4 broken on simbx01
6to4 is a magic thing that is hard to debug due to the many remote places where it could go wrong (packets outbound + inbound, on both IPv4 and IPv6). Not much there can be done about this.
The main thing that one should do though: don't use 6to4.
6to4 is great for temporary setups, they sometimes work, but when it breaks debugging it becomes unfeasible without having access to every single IPv4 and IPv6 hop in the path.
|
![[ch]](/s/countries/ch.gif)
on Monday, 22 February 2010 08:24:18
Posting is only allowed when you are