I spend last couple of days setting up OpenWRT and IPv6 on my router and managed to have to have it assign IPv6 addresses to computers on wired LAN using aiccu, my own prefix and radvd. I couldn't set them up on wireless, but my question isn't about that. My problem is that since today, I can't get IPv6 access using aiccu. Settings worked up until yesterday, but since this morning, I can't get it to work. Here's output of aiccu autotest using configuration file that worked: root@OpenWrt:/etc# aiccu autotest /etc/aiccu.conf.old ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (77.105.40.140) ### 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 77.105.40.140 (77.105.40.140): 56 data bytes 64 bytes from 77.105.40.140: seq=0 ttl=64 time=0.358 ms 64 bytes from 77.105.40.140: seq=1 ttl=64 time=0.215 ms 64 bytes from 77.105.40.140: seq=2 ttl=64 time=0.229 ms --- 77.105.40.140 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.215/0.267/0.358 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (212.18.63.73) ### 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 212.18.63.73 (212.18.63.73): 56 data bytes 64 bytes from 212.18.63.73: seq=0 ttl=53 time=34.494 ms 64 bytes from 212.18.63.73: seq=1 ttl=53 time=34.104 ms 64 bytes from 212.18.63.73: seq=2 ttl=53 time=33.269 ms --- 212.18.63.73 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 33.269/33.955/34.494 ms ###### ####### [3/8] Traceroute to the PoP (212.18.63.73) 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.18.63.73 (212.18.63.73), 30 hops max, 38 byte packets 1 192.168.2.1 (192.168.2.1) 1.322 ms 0.890 ms 0.825 ms 2 77.105.0.231 (77.105.0.231) 10.865 ms 8.919 ms 10.460 ms 3 catalyst-12t.sezampro.rs (77.105.0.222) 9.440 ms 9.291 ms 9.562 ms 4 sezampro-bcn.telekom.yu (195.178.34.5) 10.368 ms 11.820 ms 10.209 ms 5 te1-3.ccr01.bud03.atlas.cogentco.com (149.6.182.21) 16.607 ms 18.398 ms 15.316 ms 6 te3-3.ccr01.bud01.atlas.cogentco.com (130.117.3.73) 15.434 ms te2-4.ccr01.bud01.atlas.cogentco.com (130.117.48.225) 15.094 ms te4-8.ccr01.bud01.atlas.cogentco.com (154.54.37.138) 15.706 ms 7 te4-8.ccr02.bts01.atlas.cogentco.com (154.54.38.190) 22.489 ms 25.991 ms 265.000 ms 8 te1-2.ccr01.vie01.atlas.cogentco.com (130.117.51.129) 26.200 ms te4-2.ccr01.vie01.atlas.cogentco.com (130.117.49.26) 26.359 ms te1-2.ccr01.vie01.atlas.cogentco.com (130.117.51.129) 23.478 ms 9 te1-2.ccr01.lju01.atlas.cogentco.com (130.117.48.82) 28.977 ms 29.709 ms 29.731 ms 10 149.6.52.34 (149.6.52.34) 30.843 ms 149.6.52.38 (149.6.52.38) 35.037 ms 149.6.52.34 (149.6.52.34) 30.159 ms 11 maribor3-te-1-1.amis.net (212.18.35.233) 35.324 ms 33.724 ms 34.309 ms 12 simbx01.sixxs.net (212.18.63.73) 40.579 ms 35.046 ms 35.427 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.354 ms 64 bytes from ::1: seq=1 ttl=64 time=0.290 ms 64 bytes from ::1: seq=2 ttl=64 time=0.308 ms --- ::1 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.290/0.317/0.354 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:15c0:65ff:419::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:15c0:65ff:419::2 (2001:15c0:65ff:419::2): 56 data bytes 64 bytes from 2001:15c0:65ff:419::2: seq=0 ttl=64 time=0.397 ms 64 bytes from 2001:15c0:65ff:419::2: seq=1 ttl=64 time=0.350 ms 64 bytes from 2001:15c0:65ff:419::2: seq=2 ttl=64 time=0.354 ms --- 2001:15c0:65ff:419::2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.350/0.367/0.397 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:15c0:65ff:419::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:15c0:65ff:419::1 (2001:15c0:65ff:419::1): 56 data bytes --- 2001:15c0:65ff:419::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. sh: traceroute6: not found ###### ###### [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 sh: traceroute6: not found ###### ###### 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. Here's output of system log when I start aiccu: Feb 21 11:36:39 OpenWrt local7.info syslog: Succesfully retrieved tunnel information for T33005 Feb 21 11:36:39 OpenWrt local7.info syslog: AICCU running as PID 3480 Feb 21 11:36:39 OpenWrt user.info kernel: sixxs: Disabled Privacy Extensions Feb 21 11:36:39 OpenWrt local7.info syslog: [AYIYA-start] : Anything in Anything (draft-02) Feb 21 11:36:39 OpenWrt local7.info syslog: [AYIYA-tun->tundev] : (Socket to TUN) started The router can resolve to IPv6 addresses, but I can't ping anything, as can be seen from autotest. If I get the instructions correctly, if I'm having problems with SixXs service, I should contact them directly. I'm trying to figure out if its me or them.