aiccu test

####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (62.12.194.141) ### 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 62.12.194.141 (62.12.194.141): 56 data bytes 64 bytes from 62.12.194.141: seq=0 ttl=64 time=0.268 ms 64 bytes from 62.12.194.141: seq=1 ttl=64 time=0.187 ms 64 bytes from 62.12.194.141: seq=2 ttl=64 time=0.219 ms --- 62.12.194.141 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.187/0.224/0.268 ms ###### Did this work? [Y/n] ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.144.148.74) ### 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 213.144.148.74 (213.144.148.74): 56 data bytes 64 bytes from 213.144.148.74: seq=0 ttl=59 time=16.738 ms 64 bytes from 213.144.148.74: seq=1 ttl=59 time=16.867 ms 64 bytes from 213.144.148.74: seq=2 ttl=59 time=17.045 ms --- 213.144.148.74 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 16.738/16.883/17.045 ms ###### Did this work? [Y/n] ####### [3/8] Traceroute to the PoP (213.144.148.74) 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 213.144.148.74 (213.144.148.74), 30 hops max, 38 byte packets 1 zhtix2-lns2.cyberlink.ch (212.55.222.62) 16.781 ms 17.166 ms 16.638 ms 2 zhtix2-pe1-zhtix2-sg1.cyberlink.ch (213.158.128.153) 16.500 ms 24.473 ms 16.413 ms 3 zhtix1-br1-zhtix2-pe1.cyberlink.ch (212.55.223.21) 40.532 ms 16.787 ms 16.652 ms 4 r1zur1.core.init7.net (77.109.134.9) 16.169 ms 16.564 ms 16.411 ms 5 r1zlz1.core.init7.net (77.109.128.210) 16.868 ms 24.214 ms 25.219 ms 6 chzrh02.sixxs.net (213.144.148.74) 16.409 ms 16.811 ms 16.664 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: seq=0 ttl=64 time=0.269 ms 64 bytes from ::1: seq=1 ttl=64 time=0.232 ms 64 bytes from ::1: seq=2 ttl=64 time=0.234 ms --- ::1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.232/0.245/0.269 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1620:f00:153::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:1620:f00:153::2 (2001:1620:f00:153::2): 56 data bytes 64 bytes from 2001:1620:f00:153::2: seq=0 ttl=64 time=0.296 ms 64 bytes from 2001:1620:f00:153::2: seq=1 ttl=64 time=0.346 ms 64 bytes from 2001:1620:f00:153::2: seq=2 ttl=64 time=0.257 ms --- 2001:1620:f00:153::2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.257/0.299/0.346 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1620:f00:153::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:1620:f00:153::1 (2001:1620:f00:153::1): 56 data bytes --- 2001:1620:f00:153::1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss ###### Did this work? [Y/n] n