Hi, currently the tunnel is unreachable although nothing else changed as far as I can tell. Aiccu starts and correctly finds the pop and assigns the addresses, but pinging the other tunnel endpoint from the client does not return anything. Pinging kame also does not return any packet. Pinging either tunnel endpoint from remote (DFN) returns From 2a01:198:200::2 icmp_seq=1 Destination unreachable: No route. TCPDUMP shows indeed outgoing udp packages but no replies coming in. This is behind a speedport W920V where it worked for a while. Automatic firmware updates are disabled. Local time looks correct and is maintained by ntp. There are not ipv4 firewall rules and ipv6 rules only apply to forwarded traffic and thus accept anything incoming. Tunnel Information for T20899: POP Id : dedus01 IPv6 Local : 2a01:198:200:479::2/64 IPv6 Remote : 2a01:198:200:479::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.250) ### 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.250 (192.168.1.250) 56(84) bytes of data. 64 bytes from 192.168.1.250: icmp_req=1 ttl=64 time=0.081 ms 64 bytes from 192.168.1.250: icmp_req=2 ttl=64 time=0.055 ms 64 bytes from 192.168.1.250: icmp_req=3 ttl=64 time=0.051 ms --- 192.168.1.250 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.051/0.062/0.081/0.014 ms ###### ####### [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=56 time=31.2 ms 64 bytes from 91.184.37.98: icmp_req=2 ttl=56 time=31.1 ms 64 bytes from 91.184.37.98: icmp_req=3 ttl=56 time=31.3 ms --- 91.184.37.98 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 31.161/31.272/31.371/0.221 ms ###### ####### [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.box (192.168.1.10) 0.653 ms 0.720 ms 0.872 ms 2 87.186.224.135 (87.186.224.135) 19.578 ms 19.701 ms 20.023 ms 3 87.190.178.206 (87.190.178.206) 22.665 ms 22.557 ms 22.476 ms 4 hh-ea4-i.HH.DE.NET.DTAG.DE (62.154.33.34) 111.372 ms 111.457 ms 111.388 ms 5 hbg-b2-link.telia.net (213.248.103.165) 26.934 ms 80.156.161.122 (80.156.161.122) 29.360 ms 29.300 ms 6 hbg-bb1-link.telia.net (80.91.246.6) 28.824 ms hbg-bb2-link.telia.net (80.91.251.81) 28.827 ms hbg-bb1-link.telia.net (80.91.246.6) 28.670 ms 7 ddf-b2-link.telia.net (80.91.247.15) 34.572 ms 30.784 ms ddf-b2-link.telia.net (213.248.65.110) 32.455 ms 8 speedpartner-106633-ddf-b1.c.telia.net (213.248.68.130) 31.949 ms 31.258 ms 31.312 ms 9 dedus01.sixxs.net (91.184.37.98) 32.721 ms 31.144 ms 31.014 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.057 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.047 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.079 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 0.047/0.061/0.079/0.013 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:198:200:479::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2a01:198:200:479::2(2a01:198:200:479::2) 56 data bytes 64 bytes from 2a01:198:200:479::2: icmp_seq=1 ttl=64 time=0.049 ms 64 bytes from 2a01:198:200:479::2: icmp_seq=2 ttl=64 time=0.067 ms 64 bytes from 2a01:198:200:479::2: icmp_seq=3 ttl=64 time=0.054 ms --- 2a01:198:200:479::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1999ms rtt min/avg/max/mdev = 0.049/0.056/0.067/0.011 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:198:200:479::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:479::1(2a01:198:200:479::1) 56 data bytes --- 2a01:198:200:479::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms ###### ###### [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 * * * 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, 80 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) ### 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. -- /etc/init.d/aiccu start Tunnel Information for T20899: POP Id : dedus01 IPv6 Local : 2a01:198:200:479::2/64 IPv6 Remote : 2a01:198:200:479::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled -- tcpdump -n host 91.184.37.98 & ping6 www.kame.net PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes 10:27:24.317594 IP 192.168.1.250.36450 > 91.184.37.98.5072: UDP, length 148 10:27:25.319477 IP 192.168.1.250.36450 > 91.184.37.98.5072: UDP, length 148 10:27:26.314074 IP 192.168.1.250.36450 > 91.184.37.98.5072: UDP, length 148 ^C --- www.kame.net ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2013ms -- ifconfig eth0 eth0 Link encap:Ethernet HWaddr 54:52:00:46:bd:eb inet addr:192.168.1.250 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::5652:ff:fe46:bdeb/64 Scope:Link inet6 addr: fec0::250/64 Scope:Site inet6 addr: 2a01:198:45f::250/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:71344084 errors:0 dropped:0 overruns:0 frame:0 TX packets:74037715 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:36714810642 (34.1 GiB) TX bytes:38259225050 (35.6 GiB) -- route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.10 0.0.0.0 UG 0 0 0 eth0 -- ip -6 route 2a01:198:200:479::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 2a01:198:45f::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2a01:198:45f:1::/64 via fe80::219:66ff:fe92:37b4 dev eth0 proto zebra metric 101 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 fec0::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fec1::/64 via fe80::219:66ff:fe92:37b4 dev eth0 proto zebra metric 101 mtu 1500 advmss 1440 hoplimit 4294967295 default via 2a01:198:200:479::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 -- apt-cache show aiccu Package: aiccu Priority: optional Section: net Installed-Size: 228 Maintainer: Reinier Haasjes <reinier@haasjes.com> Architecture: amd64 Version: 20070115-14 Depends: debconf (>= 0.5) | debconf-2.0, libc6 (>= 2.2.5), libgnutls26 (>= 2.7.14-0), debconf, lsb-base, ucf, iputils-ping, iputils-tracepath, iproute Recommends: ntpdate | ntp | time-daemon, bind9-host | dnsutils Filename: pool/main/a/aiccu/aiccu_20070115-14_amd64.deb Size: 57480 MD5sum: 32e8a28e512eb258395390164e53aefa SHA1: e32d6c74a535865268591dbdebaa337f6efb0cb7 SHA256: 04460b43f3cca2f2f3cd1f09f27c0cc2dc5c58d4f1626e515492a02cd9d82c78 Description: SixXS Automatic IPv6 Connectivity Client Utility This client configures IPv6 connectivity without having to manually configure interfaces etc. A SixXS account or an account of another supported tunnel broker and at least one tunnel are required. These can be freely requested from the SixXS website at no cost. For more information about SixXS check their homepage. Homepage: http://www.sixxs.net/tools/aiccu/ Tag: imp -- cat /etc/aiccu.conf username MBS9-SIXXS password xxxxxxxxxx protocol tic server tic.sixxs.net tunnel_id T20899 ipv6_interface sixxs verbose true daemonize true automatic true requiretls false behindnat true Thanks, mbr