Username: Password:

Ticket ID: SIXXS #2600133
Ticket Status: Resolved

PoP: gblon02 - Goscomb Technologies (London)

T21232 - 100% packet loss to remote endpoint
[gb] Philipp Meyerhoefer on Saturday, 11 September 2010 15:27:21
ip6 works fine when enabling miredo on linux, but not with the tunnel (used to work alright until yesterday) ~$ sudo aiccu test Tunnel Information for T21232: POP Id : gblon02 IPv6 Local : 2a01:348:6:1ff::2/64 IPv6 Remote : 2a01:348:6:1ff::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.100) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data. 64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=0.043 ms 64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=0.061 ms 64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=0.061 ms --- 192.168.1.100 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.043/0.055/0.061/0.008 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (77.75.104.126) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur PING 77.75.104.126 (77.75.104.126) 56(84) bytes of data. 64 bytes from 77.75.104.126: icmp_seq=1 ttl=57 time=27.4 ms 64 bytes from 77.75.104.126: icmp_seq=2 ttl=57 time=27.9 ms 64 bytes from 77.75.104.126: icmp_seq=3 ttl=57 time=29.7 ms --- 77.75.104.126 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 27.481/28.392/29.749/0.997 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (77.75.104.126) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem traceroute to 77.75.104.126 (77.75.104.126), 30 hops max, 40 byte packets 1 dsldevice.lan (192.168.1.254) 46.131 ms 44.316 ms 42.521 ms 2 lo0-central1.thn-ag2.plus.net (195.166.128.229) 33.572 ms 36.669 ms 53.766 ms 3 gi1-10-211.thn-gw1.plus.net (84.92.6.192) 53.884 ms 54.069 ms 54.263 ms 4 te3-2.ptn-gw01.plus.net (212.159.1.53) 54.373 ms 57.653 ms 57.751 ms 5 te3-1.ptn-gw02.plus.net (212.159.1.110) 140.864 ms 143.015 ms 143.196 ms 6 ae0-461.rt0.sov.uk.goscomb.net (195.66.226.226) 77.978 ms 44.977 ms 44.196 ms 7 ae0-1624.rt2.the.uk.goscomb.net (77.75.109.161) 31.341 ms 36.912 ms 27.648 ms 8 gblon02.sixxs.net (77.75.104.126) 39.560 ms 39.596 ms 43.315 ms ###### Did this work? [Y/n] y ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.058 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.066 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.068 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.058/0.064/0.068/0.004 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:348:6:1ff::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2a01:348:6:1ff::2(2a01:348:6:1ff::2) 56 data bytes 64 bytes from 2a01:348:6:1ff::2: icmp_seq=1 ttl=64 time=0.066 ms 64 bytes from 2a01:348:6:1ff::2: icmp_seq=2 ttl=64 time=0.076 ms 64 bytes from 2a01:348:6:1ff::2: icmp_seq=3 ttl=64 time=0.077 ms --- 2a01:348:6:1ff::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 0.066/0.073/0.077/0.005 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:348:6:1ff::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall of course ### If the previous test was succesful then this could be both ### a firewalling and a routing/interface problem PING 2a01:348:6:1ff::1(2a01:348:6:1ff::1) 56 data bytes --- 2a01:348:6:1ff::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2010ms ###### Did this work? [Y/n] n
T21232 - 100% packet loss to remote endpoint
[gb] Philipp Meyerhoefer on Sunday, 12 September 2010 03:22:28
please close this ticket, issue disappeared meanwhile.
State change: resolved
[ch] Jeroen Massar SixXS Staff on Monday, 13 September 2010 18:54:06
Message is Locked
The state of this ticket has been changed to resolved

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

Not logged in.
©2001-2014 SixXS - IPv6 Deployment & Tunnel Broker