Hello, I wanted to share my recent experience. I was trying to setup ayiya tunnel using my Linksys WRT320N patched with DD-WRT(big)v24 (running kernel 2.6.24.111), i spent hours .. and hours ... and hours ... trying to setup the tunnel, following multiple guidelines ... unsuccessfully. Finally, i decided to try setting aiccu on my laptop (Ubuntu10.10), and WOW ... 5 seconds of work and everything was fine. I just had to insall AICCU package and give user/password informations. So ... why should it be the same (or about) inside DD-WRT ? Many tutorials talk about startup scripts where it is needed to create a tunnel interface, and many other things ... but ity was not the case for me. What I had to do: - Add ipk packages ( ipv6.ko, ip6tables.ko, sit.ko and ip6table_mod_filter.ko ) matching the kernel version ( 2.6.24.111 ). - Loading those packages using "insmod" command. - Add aiccu package ( using ipkg -force-depends install ) command to avoid installation error due to kernell version mismatch. - Add iputils-ping6 and iputils-traceroute6 packages (not mandatory, but usefull to test connectivity and needed to use the aiccu test command). - Create a startup script: # Enable Jffs and mount network share nvram set sys_enable_jffs2=1 mount.cifs //<my server ip>/jffs /jffs -o username=<login>,password=<password> # loading mods, it seems that a small pause help things go smoother insmod /jffs/lib/modules/2.6.24.111/ipv6.ko sleep 1 insmod sit sleep 1 insmod /jffs/lib/modules/2.6.24.111/ip6tables.ko insmod /jffs/lib/modules/2.6.24.111/ip6table_filter.ko sleep 5 # update kernel clock, needed for aiccu to start ntpclient pool.ntp.org #lauch aiccu sleep 5 /jffs/usr/sbin/aiccu start /jffs/etc/aiccu.conf After reboot my tunnel was up and working. So, don't follow tutorials blindly, each situation is unique.