BTW, it's a bit frustrating to have just a little bit of IPv6 support, but none of the real tools that are needed, like ping6, ip6tables, etc. How would I go about making a request to have those things included in the category of IPv6 support, and where can I get versions of them that will work on the image I'm using?
Doug
Last edited by dougb on Sun Feb 07, 2010 8:23; edited 1 time in total
Posted: Sun Feb 07, 2010 8:22 Post subject: Solved!
I'm a bit embarrassed, but happy that I figured out my mistake. It turns out that the /64 prefix for the tunnel is subtly different from the /64 prefix for the actual routed addresses. For example, if your tunnel endpoint ("Client IPv6 address" on the Tunnel Details page) is 2001:470:xxx1:abcd::2/64 your routed /64 (and therefore the prefix you need for radvd.conf!) is likely going to be 2001:470:xxx2:abcd::/64 ("Routed /64" on the tunnel details page). Once I got this bit fixed I was all set. This also explains why it accidentally worked for me a few times previously. The last time I did this I actually used my routed /48 (which has a totally different prefix) so I didn't run into this problem.
I hope this saves someone the hours (eek) of frustration that I experienced.
I should also say explicitly how much I appreciate those in the community who have contributed suggestions that I cribbed from in the above, especially crushedhat.
Doug
Last edited by dougb on Fri Aug 03, 2012 8:50; edited 1 time in total
Joined: 29 Nov 2009 Posts: 354 Location: Dark Side of the Moon
Posted: Sat Feb 13, 2010 17:21 Post subject: This code works!
This code works on a wrt160n v3 the only thing I did that isn't on here is enable jffs in telnet. I'm not sure why but radvd wouldn't work without doing that.
Run this script in telnet and it will enable jffs on this firmware.
nvram set jffs_mounted=1
nvram set enable_jffs2=1
nvram set sys_enable_jffs2=1
nvram set clean_jffs2=1
nvram set sys_clean_jffs2=1
nvram commit
reboot
If it's not needed please reply and say so, but I just know that after running this script the code in the thread above works fine.
Just an addition jffs2 is not needed to enable ipv6. When I upgraded to the next build I did not have to enable it.
You're running a different firmware than I am, so that may account for the difference. It was not necessary for me to enable jffs. What I did have to do (that I forgot to mention, sorry) was to input the radvd.conf into the web interface so that it would get created at each boot.
Joined: 29 Nov 2009 Posts: 354 Location: Dark Side of the Moon
Posted: Sun Feb 14, 2010 14:16 Post subject: Thanks for the info.
I thought I was having the same problem and messed with it for a few hours trying to fix the problem and nothing worked. Turned out that my wireless connection status was not detecting the ipv6. After working on it for a while I went to the Kame project and the turtle was dancing even though my wireless connection status said I had no ipv6 internet. Must be a problem with the program or the wireless card driver. Thanks for the info. There are probably a lot of other wrt160n v3 owners out there that can use this info for their own HE tunnels. Kudos.
echo "Configuring tunnel, remote $TIP local $WIP" > /tmp/ipv6-startup.debug
ip tunnel add he-ipv6 mode sit remote $TIP local $WIP ttl 255
ip link set he-ipv6 up
ip addr add ${TUNNEL}::2/64 dev he-ipv6
ip route add ::/0 dev he-ipv6
# Not strictly necessary, but handy
ip -f inet6 addr add ${ROUTED}::1/64 dev br0
It worked like a charm for me on the first try. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.