Hi, since this a few moments, 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 icmp unreachables replies coming in. This is behind a speedport W920V where it worked for a while. I've also rebooted the speedport to make sure NAT handling did not break. 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. -- ### 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_seq=1 ttl=56 time=30.7 ms 64 bytes from 91.184.37.98: icmp_seq=2 ttl=56 time=30.9 ms 64 bytes from 91.184.37.98: icmp_seq=3 ttl=56 time=31.3 ms --- 91.184.37.98 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2010ms rtt min/avg/max/mdev = 30.715/30.980/31.306/0.245 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, 40 byte packets 1 speedport.ip (192.168.1.10) 0.477 ms 0.509 ms 0.515 ms 2 (87.186.224.135) 19.405 ms 20.307 ms 20.201 ms 3 (87.190.178.198) 22.006 ms 22.302 ms 22.179 ms 4 (62.154.33.34) 25.900 ms 26.117 ms 26.343 ms 5 (80.156.161.122) 27.189 ms (213.248.103.165) 27.504 ms (80.156.161.122) 27.722 ms 6 (80.91.251.77) 28.038 ms 26.130 ms (80.91.246.8) 26.313 ms 7 (213.248.65.110) 33.572 ms (80.91.251.192) 39.008 ms (213.248.65.110) 30.928 ms 8 (213.248.68.130) 32.811 ms 33.142 ms 34.161 ms 9 (91.184.37.98) 33.579 ms 34.015 ms 34.335 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.054 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.037 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.047 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 0.037/0.046/0.054/0.007 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.047 ms 64 bytes from 2a01:198:200:479::2: icmp_seq=2 ttl=64 time=0.045 ms 64 bytes from 2a01:198:200:479::2: icmp_seq=3 ttl=64 time=0.053 ms --- 2a01:198:200:479::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.045/0.048/0.053/0.006 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 succesful 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 2014ms ###### ###### [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) ### 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 Starting SixXS Automatic IPv6 Connectivity Client Utility (aiccu)...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 7 packets transmitted, 0 received, 100% packet loss, time 6030ms 17:16:09.911489 IP 192.168.1.250.42548 > 91.184.37.98.5072: UDP, length 148 17:16:09.943530 IP 91.184.37.98 > 192.168.1.250: ICMP 91.184.37.98 udp port 5072 unreachable, length 184 -- ifconfig eth0 eth0 Link encap:Ethernet Hardware Adresse 54:52:00:46:bd:eb inet Adresse:192.168.1.250 Bcast:192.168.1.255 Maske:255.255.255.0 inet6-Adresse: fe80::5652:ff:fe46:bdeb/64 Gltigkeitsbereich:Verbindung inet6-Adresse: fec0::250/64 Gltigkeitsbereich:Standort inet6-Adresse: 2a01:198:45f::250/64 Gltigkeitsbereich:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX packets:25581 errors:0 dropped:0 overruns:0 frame:0 TX packets:27598 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlnge:1000 RX bytes:9097384 (8.6 MiB) TX bytes:10083397 (9.6 MiB) route -n Kernel-IP-Routentabelle Ziel Router 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 metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 2a01:198:45f::/64 dev eth0 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 metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 fec0::/64 dev eth0 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: 208 Maintainer: Philipp Kern <pkern@debian.org> Architecture: amd64 Version: 20070115-9 Depends: libc6 (>= 2.7-1), libgnutls26 (>= 2.4.0-0), iputils-ping, iputils-tracepath, iproute, debconf, lsb-base Recommends: ntpdate | ntp | time-daemon Filename: pool/main/a/aiccu/aiccu_20070115-9_amd64.deb Size: 51970 MD5sum: 12ffd6790e2e240f1fafcce78d236a6c SHA1: d97b08b55dda607d08ef65c421d11375df1a00ff SHA256: eaf11445995a74e9f87daa55414ffe146eb8a48ec1b92bcd1d2eb2ee910dfcdb 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: implemented-in::c, interface::daemon, network::routing, network::vpn, protocol::ipv6, role::program -- # /etc/aiccu.conf username MBS9-SIXXS password xxxxxx protocol tic server tic.sixxs.net tunnel_id T20899 ipv6_interface sixxs verbose true daemonize true automatic true requiretls false behindnat true Thanks, mbr