Username: Password:

Ticket ID: SIXXS #6900294
Ticket Status: Invalid

PoP: deham02 - Easynet (Hamburg)

Problem reaching T23991 PoP
[de] Kai Uwe Jesussek on Thursday, 26 April 2012 21:29:33
Dear SixXS support, I've got some problems with the deham02 PoP. Problems started in february, with temporarly unpingable PoP. But since monday I'm unable to ping my PoP or any other ipv6 address after the tunnel started. Following the result of aiccu test: ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.2) ### 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.2 (192.168.1.2): 56 data bytes 64 bytes from 192.168.1.2: seq=0 ttl=64 time=0.351 ms 64 bytes from 192.168.1.2: seq=1 ttl=64 time=0.259 ms 64 bytes from 192.168.1.2: seq=2 ttl=64 time=0.221 ms --- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.221/0.277/0.351 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.189) ### 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 212.224.0.189 (212.224.0.189): 56 data bytes 64 bytes from 212.224.0.189: seq=0 ttl=53 time=33.167 ms 64 bytes from 212.224.0.189: seq=1 ttl=53 time=33.252 ms 64 bytes from 212.224.0.189: seq=2 ttl=53 time=32.422 ms --- 212.224.0.189 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 32.422/32.947/33.252 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (212.224.0.189) 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 212.224.0.189 (212.224.0.189), 30 hops max, 38 byte packets 1 192.168.1.1 (192.168.1.1) 0.264 ms 0.157 ms 0.142 ms 2 * * * 3 83-169-155-62.static.superkabel.de (83.169.155.62) 25.421 ms 10.874 ms 9.944 ms 4 88-134-196-150-dynip.superkabel.de (88.134.196.150) 10.265 ms 10.664 ms 9.142 ms 5 88-134-202-122-dynip.superkabel.de (88.134.202.122) 413.513 ms 28.953 ms 24.082 ms 6 88-134-202-17-dynip.superkabel.de (88.134.202.17) 22.542 ms 22.853 ms 36.550 ms 7 te0-0-0-5.er10.ixfra.de.easynet.net (80.81.192.14) 24.941 ms 24.633 ms 23.679 ms 8 te3-1-0.gr11.kgham.de.easynet.net (87.86.77.63) 32.051 ms 34.406 ms 31.913 ms 9 te3-1.111.br40.kgham.de.easynet.net (87.86.69.223) 27.609 ms 27.821 ms 27.001 ms 10 ge1-15.br2.isham.de.easynet.net (212.224.4.196) 27.044 ms 28.697 ms 26.365 ms 11 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 27.419 ms 26.423 ms 26.586 ms 12 212.224.0.189 (212.224.0.189) 32.472 ms 31.696 ms 33.154 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: seq=0 ttl=64 time=0.378 ms 64 bytes from ::1: seq=1 ttl=64 time=0.343 ms 64 bytes from ::1: seq=2 ttl=64 time=0.291 ms --- ::1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.291/0.337/0.378 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:1c00:100::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:6f8:1c00:100::2 (2001:6f8:1c00:100::2): 56 data bytes 64 bytes from 2001:6f8:1c00:100::2: seq=0 ttl=64 time=0.418 ms 64 bytes from 2001:6f8:1c00:100::2: seq=1 ttl=64 time=0.363 ms 64 bytes from 2001:6f8:1c00:100::2: seq=2 ttl=64 time=0.332 ms --- 2001:6f8:1c00:100::2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.332/0.371/0.418 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:1c00:100::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 2001:6f8:1c00:100::1 (2001:6f8:1c00:100::1): 56 data bytes --- 2001:6f8:1c00:100::1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss ###### Did this work? [Y/n] n
State change: invalid
[ch] Jeroen Massar SixXS Staff on Friday, 27 April 2012 07:46:10
Message is Locked
The state of this ticket has been changed to invalid
Problem reaching T23991 PoP
[ch] Jeroen Massar SixXS Staff on Friday, 27 April 2012 07:50:58
Please read and follow the "Reporting Problems" section on the Contact page and provide more details. Aiccu test only determines tht something is broken, nothing else. Note that you have a heartbeat tunnel and a RFC1918 based address, this is typically incompatible. See the FAQ for more details.

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

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