Dear SixXS-Staff, AYIYA over the pop chzrh02 seems to be broken. When I start aiccu, the tunnel T50381 is established without errors but pings to the remote IPv6 endpoint or another IPv6 adresses won't work. Tcpdump shows ping6 requests going through the tunnel but no replies are coming backs. The other static tunnel T51165 I have over the chzrh02 responds to pings without problems. Regards, Sebastian tumtum:~# ifconfig sixxs sixxs Link encap:UNSPEC Hardware Adresse 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6-Adresse: 2001:1620:f00:d8::2/64 Gltigkeitsbereich:Global inet6-Adresse: fe80::1420:f00:d8:2/64 Gltigkeitsbereich:Verbindung UP PUNKTZUPUNKT RUNNING NOARP MULTICAST MTU:1280 Metrik:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlnge:500 RX bytes:0 (0.0 B) TX bytes:208 (208.0 B) tumtum:~# ip -6 route list | grep default default via 2001:1620:f00:d8::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 tumtum:~# iptables -v -n -L | grep 213.144.148.74 0 0 ACCEPT 41 -- * * 213.144.148.74 0.0.0.0/0 tumtum:~# aiccu autotest Tunnel Information for T50381: POP Id : chzrh02 IPv6 Local : 2001:1620:f00:d8::2/64 IPv6 Remote : 2001:1620:f00:d8::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.13) ### 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.1.13 (192.168.1.13) 56(84) bytes of data. 64 bytes from 192.168.1.13: icmp_seq=1 ttl=64 time=0.094 ms 64 bytes from 192.168.1.13: icmp_seq=2 ttl=64 time=0.057 ms 64 bytes from 192.168.1.13: icmp_seq=3 ttl=64 time=0.063 ms --- 192.168.1.13 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.057/0.071/0.094/0.017 ms ###### ####### [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(84) bytes of data. 64 bytes from 213.144.148.74: icmp_seq=1 ttl=55 time=9.46 ms 64 bytes from 213.144.148.74: icmp_seq=2 ttl=55 time=9.67 ms 64 bytes from 213.144.148.74: icmp_seq=3 ttl=55 time=9.34 ms --- 213.144.148.74 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2005ms rtt min/avg/max/mdev = 9.346/9.496/9.674/0.135 ms ###### ####### [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, 40 byte packets 1 pumpum.local (192.168.1.1) 0.964 ms 1.458 ms 1.920 ms 2 212.161.178.96 (212.161.178.96) 22.339 ms * * 3 194.230.94.241 (194.230.94.241) 10.581 ms 12.043 ms 13.003 ms 4 * * * 5 * * * 6 212.161.252.110 (212.161.252.110) 23.566 ms 212.161.249.126 (212.161.249.126) 23.595 ms 212.161.252.110 (212.161.252.110) 24.165 ms 7 swissix-glb.init7.net (91.206.52.3) 34.063 ms 212.161.252.110 (212.161.252.110) 21.626 ms swissix-glb.init7.net (91.206.52.3) 24.067 ms 8 swissix-glb.init7.net (91.206.52.3) 23.342 ms r1oer1.core.init7.net (77.109.128.177) 9.018 ms 9.295 ms 9 r1zur1.core.init7.net (77.109.128.253) 10.647 ms r1oer1.core.init7.net (77.109.128.177) 13.063 ms r1zur1.core.init7.net (77.109.128.253) 12.523 ms 10 r1zur1.core.init7.net (77.109.128.253) 26.035 ms 14.336 ms 26.189 ms 11 chzrh02.sixxs.net (213.144.148.74) 17.044 ms 17.972 ms 19.189 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: icmp_seq=1 ttl=64 time=0.076 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.058 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 1999ms rtt min/avg/max/mdev = 0.058/0.068/0.076/0.007 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1620:f00:d8::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:1620:f00:d8::2(2001:1620:f00:d8::2) 56 data bytes 64 bytes from 2001:1620:f00:d8::2: icmp_seq=1 ttl=64 time=0.081 ms 64 bytes from 2001:1620:f00:d8::2: icmp_seq=2 ttl=64 time=0.067 ms 64 bytes from 2001:1620:f00:d8::2: icmp_seq=3 ttl=64 time=0.059 ms --- 2001:1620:f00:d8::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.059/0.069/0.081/0.009 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1620:f00:d8::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:d8::1(2001:1620:f00:d8::1) 56 data bytes --- 2001:1620:f00:d8::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2013ms ###### ###### [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, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### ###### [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, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### ###### ACCU Quick Connectivity Test (done)