SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #8111850
Ticket Status: Resolved

PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)

dedus01.sixxs.net is down
[de] Shadow Hawkins on Sunday, 28 October 2012 09:45:49
Hello! POP dedus01 seems to be down - for T49557. Aiccu test: aiccu test ioctl: No buffer space available RTNETLINK answers: File exists RTNETLINK answers: File exists ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.245.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.245.2 (192.168.245.2) 56(84) bytes of data. 64 bytes from 192.168.245.2: icmp_seq=1 ttl=64 time=1.99 ms 64 bytes from 192.168.245.2: icmp_seq=2 ttl=64 time=0.094 ms 64 bytes from 192.168.245.2: icmp_seq=3 ttl=64 time=0.052 ms --- 192.168.245.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.052/0.713/1.993/0.905 ms ###### Did this work? [Y/n] Y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (91.184.37.98) ### 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 91.184.37.98 (91.184.37.98) 56(84) bytes of data. 64 bytes from 91.184.37.98: icmp_seq=1 ttl=56 time=28.2 ms 64 bytes from 91.184.37.98: icmp_seq=2 ttl=56 time=30.1 ms 64 bytes from 91.184.37.98: icmp_seq=3 ttl=56 time=27.9 ms --- 91.184.37.98 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 27.987/28.801/30.194/0.999 ms ###### Did this work? [Y/n] Y ####### [3/8] Traceroute to the PoP (91.184.37.98) 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 91.184.37.98 (91.184.37.98), 30 hops max, 40 byte packets 1 192.168.245.99 (192.168.245.99) 0.314 ms 0.330 ms 0.198 ms 2 * * * 3 83-169-156-190.static.superkabel.de (83.169.156.190) 28.648 ms 29.359 ms 29.410 ms 4 88-134-196-166-dynip.superkabel.de (88.134.196.166) 29.670 ms 29.688 ms 29.608 ms 5 83-169-128-126.static.superkabel.de (83.169.128.126) 76.248 ms 76.213 ms 76.210 ms 6 88-134-202-17-dynip.superkabel.de (88.134.202.17) 66.604 ms 66.836 ms 66.813 ms 7 decix.r1.fra3.opencarrier.eu (80.81.192.24) 44.063 ms 25.876 ms 36.027 ms 8 oc-fra.speedpartner.de (194.54.95.218) 35.960 ms 35.665 ms 35.568 ms 9 dedus01.sixxs.net (91.184.37.98) 35.554 ms 31.686 ms 32.072 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=0 ttl=64 time=1.19 ms 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.115 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.082 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 0.082/0.463/1.194/0.517 ms, pipe 2 ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:198:200:a84::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2a01:198:200:a84::2(2a01:198:200:a84::2) 56 data bytes 64 bytes from 2a01:198:200:a84::2: icmp_seq=0 ttl=64 time=0.117 ms 64 bytes from 2a01:198:200:a84::2: icmp_seq=1 ttl=64 time=0.095 ms 64 bytes from 2a01:198:200:a84::2: icmp_seq=2 ttl=64 time=0.229 ms --- 2a01:198:200:a84::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.095/0.147/0.229/0.058 ms, pipe 2 ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:198:200:a84::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:198:200:a84::1(2a01:198:200:a84::1) 56 data bytes From 2a01:198:200:a84::2 icmp_seq=1 Destination unreachable: Address unreachable From 2a01:198:200:a84::2 icmp_seq=2 Destination unreachable: Address unreachable --- 2a01:198:200:a84::1 ping statistics --- 3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2001ms ###### Did this work? [Y/n] n
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 28 October 2012 17:14:36
Message is Locked
The state of this ticket has been changed to user
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 28 October 2012 22:02:20
Message is Locked
The state of this ticket has been changed to resolved

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker