I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: Hello, Today, I wanted to use my FreeWRT box to provide IPv6 connectivity for my lan using my newly acquired subnet but even the normal ayiya tunnel won't work. Incoming seems to work as I sometimes receive ping requests from the PoP. However, the corresponding responds or other outgoing packets dont't seem to reach the PoP via the tunnel (100% loss on tunnel status graph). Firewall is set to allow udp out on all ports and now even udp in on all ports. # uname -a Linux FreeWRT 2.4.33.3 #2 Fri May 9 20:33:11 CEST 2008 mips unknown # aiccu version AICCU 2007.01.15-gui by Jeroen Massar Binary is provided by FreeWRT repository. T13814 deham1 Your IPv4 AYIYA, currently 82.212.31.125 IPv6 Prefix 2001:6f8:900:a96::1/64 PoP IPv6 2001:6f8:900:a96::1 Your IPv6 2001:6f8:900:a96::2 # aiccu test ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (82.212.31.125) ### 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 BusyBox v1.1.3 (2008.05.09-18:37+0000) multi-call binary Usage: ping [OPTION]... host Send ICMP ECHO_REQUEST packets to network hosts. Options: -c COUNT Send only COUNT pings -s SIZE Send SIZE data bytes in packets (default=56) -I IPADDR Use IPADDR as source address. -q Quiet mode, only displays output at start and when finished ###### Did this work? [Y/n] y (checked manually) ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.224.0.188) ### 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 BusyBox v1.1.3 (2008.05.09-18:37+0000) multi-call binary Usage: ping [OPTION]... host Send ICMP ECHO_REQUEST packets to network hosts. Options: -c COUNT Send only COUNT pings -s SIZE Send SIZE data bytes in packets (default=56) -I IPADDR Use IPADDR as source address. -q Quiet mode, only displays output at start and when finished ###### Did this work? [Y/n] y (checked manually) ####### [3/8] Traceroute to the PoP (212.224.0.188) 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 212.224.0.188 (212.224.0.188), 30 hops max, 38 byte packets 1 * * * 2 172.30.17.41 (172.30.17.41) 7.836 ms 8.198 ms 7.947 ms 3 172.30.17.2 (172.30.17.2) 9.907 ms 9.543 ms 9.632 ms 4 172.30.6.5 (172.30.6.5) 13.813 ms 19.809 ms 15.428 ms 5 172.30.9.90 (172.30.9.90) 13.434 ms 20.017 ms 22.549 ms 6 172.30.1.2 (172.30.1.2) 13.297 ms 13.301 ms 19.239 ms 7 172.30.30.69 (172.30.30.69) 16.379 ms 15.573 ms 16.262 ms 8 172.30.30.77 (172.30.30.77) 24.347 ms 16.010 ms 17.507 ms 9 ge4-0-0.er0.ixfra.de.easynet.net (80.81.192.14) 18.092 ms 17.147 ms 17.993 ms 10 ge1-13-140.br2.isham.de.easynet.net (212.224.4.70) 32.689 ms 34.426 ms 33.252 ms 11 ge7-1.cr20.isham.de.easynet.net (212.224.4.89) 32.656 ms 32.721 ms 33.693 ms 12 deham01.sixxs.net (212.224.0.188) 33.036 ms 33.152 ms 32.524 ms ###### Did this work? [Y/n] ###### [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: icmp6_seq=0 ttl=64 time=0.5 ms 64 bytes from ::1: icmp6_seq=1 ttl=64 time=0.3 ms 64 bytes from ::1: icmp6_seq=2 ttl=64 time=0.3 ms --- ::1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.3/0.3/0.5 ms ###### Did this work? [Y/n] ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:6f8:900:a96::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:6f8:900:a96::2 (2001:6f8:900:a96::2): 56 data bytes 64 bytes from 2001:6f8:900:a96::2: icmp6_seq=0 ttl=64 time=0.5 ms 64 bytes from 2001:6f8:900:a96::2: icmp6_seq=1 ttl=64 time=0.3 ms 64 bytes from 2001:6f8:900:a96::2: icmp6_seq=2 ttl=64 time=0.3 ms --- 2001:6f8:900:a96::2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.3/0.3/0.5 ms ###### Did this work? [Y/n] ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:6f8:900:a96::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:6f8:900:a96::1 (2001:6f8:900:a96::1): 56 data bytes --- 2001:6f8:900:a96::1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss ###### Did this work? [Y/n] n I sometimes get pinged from the PoP: IP6 2001:6f8:900:a96::1 > 2001:6f8:900:a96::2: ICMP6, echo request, seq 35846, length 64 IP6 2001:6f8:900:a96::2 > 2001:6f8:900:a96::1: ICMP6, echo reply, seq 35846, length 64 IP6 2001:6f8:900:a96::1 > 2001:6f8:900:a96::2: ICMP6, echo request, seq 35846, length 64 IP6 2001:6f8:900:a96::2 > 2001:6f8:900:a96::1: ICMP6, echo reply, seq 35846, length 64 me to pop: tunnel: IP6 2001:6f8:900:a96::2 > 2001:6f8:900:a96::1: ICMP6, echo request, seq 0, length 64 IP6 2001:6f8:900:a96::2 > 2001:6f8:900:a96::1: ICMP6, echo request, seq 256, length 64 IP6 2001:6f8:900:a96::2 > 2001:6f8:900:a96::1: ICMP6, echo request, seq 512, length 64 IP6 2001:6f8:900:a96::2 > 2001:6f8:900:a96::1: ICMP6, echo request, seq 768, length 64 wan interface: IP 82.212.31.125.1029 > 212.224.0.188.5072: UDP, length 152 IP 82.212.31.125.1029 > 212.224.0.188.5072: UDP, length 152 IP 82.212.31.125.1029 > 212.224.0.188.5072: UDP, length 152 IP 82.212.31.125.1029 > 212.224.0.188.5072: UDP, length 152 # ip -6 ro 2001:6f8:900:a96::/64 dev sixxs metric 256 fe80::/64 dev eth0 metric 256 fe80::/64 dev eth0.0 metric 256 fe80::/64 dev eth2 metric 256 fe80::/64 dev br0 metric 256 fe80::/64 dev sixxs metric 256 ff00::/8 dev eth0 metric 256 ff00::/8 dev eth0.0 metric 256 ff00::/8 dev eth2 metric 256 ff00::/8 dev br0 metric 256 ff00::/8 dev sixxs metric 256 default via 2001:6f8:900:a96::1 dev sixxs metric 1024 # ip -6 addr 1: lo: <LOOPBACK,UP> inet6 ::1/128 scope host 2: eth0: <BROADCAST,MULTICAST,UP,100> qlen 1000 inet6 fe80::21d:60ff:fe15:6332/64 scope link 4: eth2: <BROADCAST,MULTICAST,UP,100> qlen 1000 inet6 fe80::21d:60ff:fe15:6332/64 scope link 7: eth0.0: <BROADCAST,MULTICAST,UP,100> inet6 fe80::21d:60ff:fe15:6332/64 scope link 8: br0: <BROADCAST,MULTICAST,UP> inet6 fe80::21d:60ff:fe15:6332/64 scope link 11: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,100> qlen 10 inet6 2001:6f8:900:a96::2/64 scope global inet6 fe80::4f8:900:a96:2/64 scope link