Tunnel Information for T71829: POP Id : demuc02 IPv6 Local : 2001:a60:f000:16a::2/64 IPv6 Remote : 2001:a60:f000:16a::1/64 Tunnel Type : 6in4-heartbeat Adminstate : enabled Userstate : enabled add tunnel sit0 failed: 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 (212.29.7.197) ### 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 212.29.7.197 (212.29.7.197) 56(84) bytes of data. 64 bytes from 212.29.7.197: icmp_req=1 ttl=64 time=0.058 ms 64 bytes from 212.29.7.197: icmp_req=2 ttl=64 time=0.072 ms 64 bytes from 212.29.7.197: icmp_req=3 ttl=64 time=0.071 ms --- 212.29.7.197 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.058/0.067/0.072/0.006 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (62.245.150.2) ### 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 62.245.150.2 (62.245.150.2) 56(84) bytes of data. 64 bytes from 62.245.150.2: icmp_req=1 ttl=60 time=0.846 ms 64 bytes from 62.245.150.2: icmp_req=2 ttl=60 time=0.932 ms 64 bytes from 62.245.150.2: icmp_req=3 ttl=60 time=0.948 ms --- 62.245.150.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.846/0.908/0.948/0.056 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (62.245.150.2) 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 62.245.150.2 (62.245.150.2), 30 hops max, 60 byte packets 1 vlan97.gw2.teamware-gmbh.de (212.29.7.222) 1.931 ms 2.531 ms 2.873 ms 2 fe-1-0.gw5.teamware-gmbh.de (212.29.0.254) 1.118 ms 1.490 ms 1.744 ms 3 teamware-gw.m-online.net (212.18.3.113) 16.079 ms 16.081 ms 16.060 ms 4 ten0-1-0-4.r4.muc2.m-online.net (212.18.6.46) 1.095 ms 1.206 ms 1.331 ms 5 demuc02.sixxs.net (62.245.150.2) 0.966 ms 0.944 ms 0.931 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.087 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.075 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.070 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.070/0.077/0.087/0.010 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:a60:f000:16a::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:a60:f000:16a::2(2001:a60:f000:16a::2) 56 data bytes 64 bytes from 2001:a60:f000:16a::2: icmp_seq=1 ttl=64 time=0.099 ms 64 bytes from 2001:a60:f000:16a::2: icmp_seq=2 ttl=64 time=0.104 ms 64 bytes from 2001:a60:f000:16a::2: icmp_seq=3 ttl=64 time=0.101 ms --- 2001:a60:f000:16a::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.099/0.101/0.104/0.008 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:a60:f000:16a::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:a60:f000:16a::1(2001:a60:f000:16a::1) 56 data bytes 64 bytes from 2001:a60:f000:16a::1: icmp_seq=1 ttl=64 time=0.974 ms 64 bytes from 2001:a60:f000:16a::1: icmp_seq=2 ttl=64 time=0.982 ms 64 bytes from 2001:a60:f000:16a::1: icmp_seq=3 ttl=64 time=1.23 ms --- 2001:a60:f000:16a::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.974/1.063/1.235/0.126 ms ###### Did this work? [Y/n] y ###### [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), 30 hops max, 80 byte packets 1 xena.enskat.de (2001:a60:f036::10) 2172.571 ms !H 2172.526 ms !H 2172.499 ms !H ###### Did this work? [Y/n] y ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 xena.enskat.de (2001:a60:f036::10) 4.594 ms !H 4.541 ms !H 4.515 ms !H ###### Did this work? [Y/n] y ###### ACCU Quick Connectivity Test (done)