Looks like dedus01 is not working at the moment. The aiccu test works up to and including 6/8, but not 7/8. From reading earlier tickets I suspect that the pop software needs a restart. Could someone please kick it? Thanks! Cheers, Hans-Martin # aiccu test ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.178.8) ### 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.178.8 (192.168.178.8) 56(84) bytes of data. 64 bytes from 192.168.178.8: icmp_req=1 ttl=64 time=0.068 ms 64 bytes from 192.168.178.8: icmp_req=2 ttl=64 time=0.062 ms 64 bytes from 192.168.178.8: icmp_req=3 ttl=64 time=0.059 ms --- 192.168.178.8 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.059/0.063/0.068/0.003 ms ###### Did this work? [Y/n] ####### [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_req=1 ttl=54 time=65.5 ms 64 bytes from 91.184.37.98: icmp_req=2 ttl=54 time=62.9 ms 64 bytes from 91.184.37.98: icmp_req=3 ttl=54 time=65.5 ms --- 91.184.37.98 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 62.962/64.706/65.599/1.268 ms ###### Did this work? [Y/n] ####### [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, 60 byte packets 1 fritz (192.168.178.1) 4.629 ms 10.538 ms 12.779 ms 2 62.214.64.236 (62.214.64.236) 61.082 ms 63.431 ms 65.387 ms 3 62.214.104.161 (62.214.104.161) 66.697 ms 68.714 ms 70.606 ms 4 10g-9-1.dor002isp006.versatel.de (62.214.110.133) 72.956 ms 10g-8-1.dor002isp006.versatel.de (62.214.110.125) 74.342 ms 76.737 ms 5 10g-8-1.fra020isp006.versatel.de (62.214.110.146) 98.106 ms 10g-7-1.fra020isp006.versatel.de (62.214.110.130) 97.313 ms 10g-8-1.fra020isp006.versatel.de (62.214.110.146) 98.557 ms 6 decix.r1.fra3.opencarrier.eu (80.81.192.24) 89.936 ms 85.970 ms 82.933 ms 7 oc-fra.speedpartner.de (194.54.95.218) 82.354 ms 64.125 ms 63.426 ms 8 dedus01.sixxs.net (91.184.37.98) 67.613 ms 68.880 ms 70.499 ms ###### Did this work? [Y/n] ###### [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.032 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.039 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.041 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.032/0.037/0.041/0.006 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:198:200:47f::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2a01:198:200:47f::2(2a01:198:200:47f::2) 56 data bytes 64 bytes from 2a01:198:200:47f::2: icmp_seq=1 ttl=64 time=0.034 ms 64 bytes from 2a01:198:200:47f::2: icmp_seq=2 ttl=64 time=0.045 ms 64 bytes from 2a01:198:200:47f::2: icmp_seq=3 ttl=64 time=0.055 ms --- 2a01:198:200:47f::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.034/0.044/0.055/0.011 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:198:200:47f::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 successful then this could be both ### a firewalling and a routing/interface problem PING 2a01:198:200:47f::1(2a01:198:200:47f::1) 56 data bytes 64 bytes from 2a01:198:200:47f::1: icmp_seq=1 ttl=64 time=68.2 ms 64 bytes from 2a01:198:200:47f::1: icmp_seq=2 ttl=64 time=70.0 ms 64 bytes from 2a01:198:200:47f::1: icmp_seq=3 ttl=64 time=69.8 ms --- 2a01:198:200:47f::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 68.243/69.394/70.074/0.873 ms ###### Did this work? [Y/n] ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2a01:198:200:47f::2, 30 hops max, 16 byte packets 1 cl-1152.dus-01.de.sixxs.net (2a01:198:200:47f::2) 3000.39 ms !H 3000.16 ms !H 3003.98 ms !H ###### Did this work? [Y/n] n