|
Ticket ID: SIXXS #821848 Ticket Status: Remote Problem PoP: noosl01 - Availo (Oslo)
6to4 return at Oslo PoP appears to be broken
![[no]](/s/countries/no.gif) Shadow Hawkins on Tuesday, 07 October 2008 23:05:12
Hi,
We just had a report from a user with 6to4 (via the AirPort Extreme) who couldn't access our site over IPv6. (The machine in question is connected via a static tunnel to the Oslo PoP.) Some debugging showed that his packets reached us, but the return packets never reached him. He could, however, ping ipv6.google.com without problems (50ms average latency).
It seems somehow 6to4 return routing is broken for that PoP:
root@wen:~# tracepath6 2002:54d7:414b:0:21e:52ff:fe74:72d3
1?: [LOCALHOST] pmtu 1480
1: gw-63.osl-01.no.sixxs.net 2.182ms
2: 2002-sixxs.cr0-r23.ver-osl.no.ip6.p80.net 2.352ms
3: v1611-r23.cr0-r69.tc-sto.se.ip6.p80.net 9.659ms
4: no reply
5: no reply
6: no reply
7: no reply
We set up our own local 6to4 return relay on the machine, which fixed the problem instantly, but I guess this should still be fixed.
State change: remoteproblem
The state of this ticket has been changed to remoteproblem
6to4 return at Oslo PoP appears to be broken
6to4 has way too many remote issues and there are way too many possible places where it can break. It might be in the upstream network, or anywhere in the path in the middle on either the packet coming back or going there.
6to4 return at Oslo PoP appears to be broken
![[dk]](/s/countries/dk.gif) Shadow Hawkins on Thursday, 11 March 2010 20:27:15
Please reopen this, 2002::/16 gets droped at my pop(noosl01.sixxs.net). Trace stops here:
klma@klma-laptop:~$ traceroute6 2002:4df3:2f16:2::10
traceroute to 2002:4df3:2f16:2::10 (2002:4df3:2f16:2::10) from 2001:16d8:dd00:95::2, 30 hops max, 16 byte packets
1 gw-150.cph-01.dk.sixxs.net (2001:16d8:dd00:95::1) 87.228 ms 140.711 ms 60.165 ms
2 3229-sixxs.cr0-r72.gbl-cph.dk.ip6.p80.net (2001:16d8:aaaa:5::1) 157.537 ms 60.795 ms 62.216 ms
I know about the problems with 6to4, but my 6to4 host can reach anything but:
klma@Jens:~$ ping6 dkcph01.sixxs.net
PING dkcph01.sixxs.net(sixxs-cph-demarc0.cust.ip6.p80.net) 56 data bytes
^C
--- dkcph01.sixxs.net ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2015ms
klma@Jens:~$ ping6 noosl01.sixxs.net
PING noosl01.sixxs.net(sixxs-oslo-demarc0.cust.ip6.p80.net) 56 data bytes
^C
--- noosl01.sixxs.net ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6048ms
klma@Jens:~$ ping6 sesto01.sixxs.net
PING sesto01.sixxs.net(sixxs-hy-demarc0.cust.ip6.p80.net) 56 data bytes
64 bytes from sixxs-hy-demarc0.cust.ip6.p80.net: icmp_seq=2 ttl=62 time=31.5 ms
64 bytes from sixxs-hy-demarc0.cust.ip6.p80.net: icmp_seq=3 ttl=62 time=31.3 ms
64 bytes from sixxs-hy-demarc0.cust.ip6.p80.net: icmp_seq=4 ttl=62 time=31.7 ms
^C
--- sesto01.sixxs.net ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 3002ms
rtt min/avg/max/mdev = 31.373/31.543/31.705/0.135 ms
That's 2 of 3 failing. This is the only thing i have tryied that fails from 6to4 and i use it 3-4 places, for management of network equipment.
I'll bet that if you move me to sesto01.sixxs.net or even decgn01.sixxs.net it'll work perfectly for me!
Regards Klaus
6to4 return at Oslo PoP appears to be broken
Last time: we are not looking into 6to4 issues.
That you can't ping can mean a lot of things, amongst others that packets on IPv6 or IPv4 in either bi-directional path are lost somewhere.
Nothing we can do about: simply don't use 6to4.
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 08 October 2008 14:16:18
Posting is only allowed when you are