Tickets - cant ping 6to4 networks, packages hung at pop :: SixXS

Ticket ID: SIXXS #1232067
Ticket Status: Remote Problem

PoP: simbx01 - Amis (Maribor)

cant ping 6to4 networks, packages hung at pop

Shadow Hawkins on Saturday, 17 October 2009 16:19:43

Ive got some problem pinging 2002:: v6 Networks (aka 6to4) over my pop. All Packages will hung at the pop. From my host to two different 6to4 Host:

# traceroute6 kronos.42.lefant.net traceroute to kronos.42.lefant.net (2002:55d6:9459:1::117), 30 hops max, 80 byte packets 1 gw-313.mbx-01.si.sixxs.net (2001:15c0:65ff:138::1) 61.249 ms 60.879 ms 60.547 ms 2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 60.335 ms 60.253 ms 60.363 ms 3 * * * 4 * * * # traceroute6 muybridge.lefant.net traceroute to muybridge.lefant.net (2002:d5ef:cf59::1), 30 hops max, 80 byte packets 1 gw-313.mbx-01.si.sixxs.net (2001:15c0:65ff:138::1) 25.187 ms 36.023 ms 37.420 ms 2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 40.711 ms 41.772 ms 44.257 ms 3 * * * 4 * * *

from the 6to4 host to my network:

# traceroute6 2001:15c0:65ff:138::2 traceroute to 2001:15c0:65ff:138::2 (2001:15c0:65ff:138::2), 30 hops max, 40 byte packets 1 2002:55e9:3a38::1 (2002:55e9:3a38::1) 18.555 ms * * 2 ve-102.edge02.muc.infra.de.ipv6.cablesurf.de (2001:4c50:89::9) 16.836 ms 17.150 ms 17.390 ms 3 ve-999.edge01.muc.infra.de.ipv6.cablesurf.de (2001:4c50:89::5) 16.738 ms 17.318 ms 17.295 ms 4 gi-4-1-0.bbr01.muc.infra.de.ipv6.cablesurf.de (2001:4c50:89::1) 17.801 ms 18.904 ms 18.900 ms 5 Cisco-M-XXI-G2-5.Space.net (2001:7f8:2c:1000:0:a500:5539:1) 18.505 ms 18.812 ms 19.531 ms 6 Cisco-M-XXXI-Te1-7-v11.Space.Net (2001:608:0:e81::218) 19.088 ms 17.326 ms 18.242 ms 7 Cisco-M-XVI-Te1-1-v20.Space.Net (2001:608:0:e75::25) 18.357 ms 18.634 ms 19.568 ms 8 Cisco-M-VI-E5.Space.Net (2001:608:0:11::121) 18.888 ms 24.645 ms 24.000 ms 9 maribor3-te-1-3.amis.net (2001:15c0:ffff:d::5) 31.510 ms 31.478 ms 31.512 ms 10 * * *

But i can ping from my host any other v6 network, like ipv6.google.com (this works als from the 6to4 machine)

myhost# traceroute6 ipv6.google.com traceroute to ipv6.google.com (2001:4860:a005::68), 30 hops max, 80 byte packets 1 gw-313.mbx-01.si.sixxs.net (2001:15c0:65ff:138::1) 26.450 ms 28.668 ms 35.995 ms 2 maribor3-vlan-4.amis.net (2001:15c0:ffff:7::1) 39.890 ms 40.075 ms 40.173 ms 3 vienna1-te-2-2.amis.net (2001:15c0:ffff:d::6) 44.603 ms 50.296 ms 52.151 ms 4 Cisco-M-VI-Tu6.Space.Net (2001:608:0:3::218f:1) 57.724 ms 60.559 ms 69.805 ms 5 Cisco-M-XVI-Vlan10.Space.Net (2001:608:0:10::125) 51.566 ms 54.071 ms 75.117 ms 6 Cisco-M-XXXI-Te1-1-v20.Space.Net (2001:608:0:e75::29) 75.219 ms 51.110 ms 52.889 ms 7 Cisco-M-XXX-Te1-7-v11.Space.Net (2001:608:0:e81::217) 51.374 ms 44.903 ms 34.765 ms 8 2001:7f8:2c:1000:0:a501:5169:1 (2001:7f8:2c:1000:0:a501:5169:1) 43.289 ms 43.250 ms 40.756 ms 9 * * * 10 ey-in-x68.google.com (2001:4860:a005::68) 62.572 ms 63.654 ms 60.694 ms 6to4host# traceroute6 ipv6.google.com traceroute to ipv6.google.com (2001:4860:a005::68), 30 hops max, 40 byte packets 1 2002:55e9:3a38::1 (2002:55e9:3a38::1) 18.175 ms * * 2 ve-102.edge02.muc.infra.de.ipv6.cablesurf.de (2001:4c50:89::9) 16.393 ms 17.006 ms 16.998 ms 3 ve-999.edge01.muc.infra.de.ipv6.cablesurf.de (2001:4c50:89::5) 16.280 ms 16.902 ms 16.896 ms 4 gi-4-1-0.bbr01.muc.infra.de.ipv6.cablesurf.de (2001:4c50:89::1) 17.952 ms 18.275 ms * 5 gi-4-0-0.bbr01.fra.infra.de.ipv6.cablesurf.de (2001:4c50::ffff:2) 17.170 ms 17.147 ms 17.137 ms 6 de-cix20.net.google.com (2001:7f8::3b41:0:1) 20.508 ms 19.464 ms 19.416 ms 7 * * * 8 * * * 9 * * * 10 ey-in-x68.google.com (2001:4860:a005::68) 42.755 ms 42.729 ms 50.083 ms

We tested also pinging from other hosts to me and vice versa and it worked well. Some facts about my host:

#uname -a && ip a && ip r && ip -6 r Linux Clavicula 2.6.30-2-686 #1 SMP Sat Sep 26 01:16:22 UTC 2009 i686 GNU/Linux 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 00:1f:d0:a3:0d:18 brd ff:ff:ff:ff:ff:ff 3: wmaster0: <UP,LOWER_UP> mtu 0 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ieee802.11 00:22:43:2c:d5:34 brd 00:00:00:00:00:00 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:22:43:2c:d5:34 brd ff:ff:ff:ff:ff:ff inet 192.168.33.130/24 brd 192.168.33.255 scope global wlan0 inet6 fe80::222:43ff:fe2c:d534/64 scope link valid_lft forever preferred_lft forever 5: sit0: <NOARP> mtu 1480 qdisc noop state DOWN link/sit 0.0.0.0 brd 0.0.0.0 8: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500 link/[65534] inet6 2001:15c0:65ff:138::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::14c0:65ff:138:2/64 scope link valid_lft forever preferred_lft forever 192.168.33.0/24 dev wlan0 proto kernel scope link src 192.168.33.130 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.33.1 dev wlan0 2001:15c0:65ff:138::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 fe80::/64 dev wlan0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0 default via 2001:15c0:65ff:138::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0

But i really think, its not my or the 6to4 host, the pop is not routing to 6to4 networks... Thanks in advance!

State change: remoteproblem Locked

Jeroen Massar SixXS Staff

on Saturday, 17 October 2009 23:05:19

The state of this ticket has been changed to remoteproblem

cant ping 6to4 networks, packages hung at pop

Jeroen Massar SixXS Staff

on Saturday, 17 October 2009 23:06:26

Sorry, but we are really not even thinking of trying to resolve 6to4 problems. There are way too many things that can go wrong (anycast on both IPv4 and IPv6; filtering issues on both IPv4 and IPv6 etc etc etc). Solve the problem by getting real connectivity instead.

cant ping 6to4 networks, packages hung at pop

Shadow Hawkins on Tuesday, 09 March 2010 23:01:32

I don't think that this problem is remote. I'm experiencing the same thing! I also only get to the pop when i try to go to any 2002::/16 address! Regards Klaus

cant ping 6to4 networks, packages hung at pop

Jeroen Massar SixXS Staff

on Wednesday, 10 March 2010 10:46:46

Try debugging it yourself, we really do not have time nor access (you need to be able to access every IPv4 and IPv6 hop in the path) for figuring out where your packets are going and why they are not coming back.

Please note Posting is only allowed when you are logged in.