ip: SIOCADDTUNNEL: No buffer space available
ip: RTNETLINK answers: File exists
ip: RTNETLINK answers: File exists
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.4.1)
### 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.4.1 (192.168.4.1): 56 data bytes
64 bytes from 192.168.4.1: seq=0 ttl=64 time=0.435 ms
64 bytes from 192.168.4.1: seq=1 ttl=64 time=0.340 ms
64 bytes from 192.168.4.1: seq=2 ttl=64 time=0.333 ms
--- 192.168.4.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.333/0.369/0.435 ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (78.35.24.124)
### 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 78.35.24.124 (78.35.24.124): 56 data bytes
64 bytes from 78.35.24.124: seq=0 ttl=58 time=21.642 ms
64 bytes from 78.35.24.124: seq=1 ttl=58 time=21.495 ms
64 bytes from 78.35.24.124: seq=2 ttl=58 time=21.783 ms
--- 78.35.24.124 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 21.495/21.640/21.783 ms
######
####### [3/8] Traceroute to the PoP (78.35.24.124) 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 78.35.24.124 (78.35.24.124), 30 hops max, 38 byte packets
1 rdsl-koln-de02.nw.mediaways.net (213.20.58.131) 19.769 ms 19.848 ms 20.182 ms
2 xmwc-koln-de02-chan-20.nw.mediaways.net (195.71.204.78) 20.377 ms 20.429 ms 20.297 ms
3 rmwc-koln-de01-gigaet-0-1-0.nw.mediaways.net (62.53.198.161) 21.310 ms 21.733 ms 20.713 ms
4 195.71.248.54 (195.71.248.54) 23.856 ms 20.334 ms 23.024 ms
5 core-pg1-t91.netcologne.de (87.79.16.105) 19.995 ms 20.947 ms 20.271 ms
6 core-eup2-t41.netcologne.de (87.79.16.205) 20.654 ms 21.080 ms 20.960 ms
7 sixxs-pop1.netcologne.net (78.35.24.124) 20.786 ms 20.853 ms 20.328 ms
######
###### [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.459 ms
64 bytes from ::1: seq=1 ttl=64 time=0.725 ms
64 bytes from ::1: seq=2 ttl=64 time=0.440 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.440/0.541/0.725 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:xxxx:ff00:30e::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:4dd0:ff00:30e::2 (2001:4dd0:ff00:30e::2): 56 data bytes
--- 2001:4dd0:ff00:30e::2 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:xxxx:ff00:30e::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:4dd0:ff00:30e::1 (2001:4dd0:ff00:30e::1): 56 data bytes
--- 2001:4dd0:ff00:30e::1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
######
###### [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, 16 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10
* * *
11
######
###### [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, 16 byte packets
1 *
######
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
