Posted: Fri May 29, 2015 14:19 Post subject: [SOLVED] Problems getting IPv6 working on EA2700 Router
Hi everyone,
I've tried quite a few things, but nothing seems to work here. My IPv6 is provided by HE.net (Tunnelbroker), and is a /64. Right now I have it set up so that everyone *should* be getting an IPv6 address from tunnelbroker. My computer(s) have IPv6 addresses inside of my range (I believe), but my router has WAN IPv4: 67.7.24.201 IPv6: ::67.7.24.201 instead.
Firmware Version
DD-WRT v24-sp2 (01/20/15) giga - build 25974M
Kernel Version
Linux 3.10.65 #5875 Tue Jan 20 07:43:03 CET 2015 mips
Attached is a screenshot of how I have the IPv6 sub-tab under Setup configured. I do have radvd and radvd custom enabled, although they don't show up in the screenshot.
Here is the contents of my radvd.conf file from the IPv6 sub-tab:
One thing I've noticed is that my computer gets a 2001:470:1f11... address, while my router is supposed to get one that has 2001:470:1f10... in it. In the past, I believe all of my computers and devices had 1f10 in theirs.
I should note that I've tried this with nothing in the IPv6 screenshot, and just recently put something there. With nothing in the screenshot, I don't have any IPv6 address listed in the upper right hand corner.
Here's my startup config and firewall config from Administration -> Commands:
Code:
Startup
-----------------------------------
nvram set partialboots=0
nvram commit
#Hurricane Electric Tunnel Configuration
# Combination of various scripts
sleep 10
insmod ipv6
sleep 30
modprobe ipv6
ip tunnel add he-ipv6 mode sit remote 184.105.253.14 ttl 255
ip link set he-ipv6 up
ip addr add 2001:470:1f10:830::2/64 dev he-ipv6
ip route add ::/0 dev he-ipv6
ip -f inet6 addr
ip addr add 2001:470:1f11:830::/64 dev br0
sleep 5
radvd -C /tmp/radvd.conf
So, I'm totally lost here. I checked my tunnel details, and it's being updated (presumably by the router, although I do have an updater script on one of my computers). But when I check at http://www.whatismyipv6.com, it shows my IPv4 address. And I'm unable to ping or access IPv6 only sites.
Is it a matter of having dd-wrt handle dhcp6? Or is it something else? Currently, I have a raspberry pi handling my dhcp for IPv4. I could always set it up to do dhcp6 also (or set the router up to do that). If I can import (or migrate) my dnsmasq configurations from the raspberry pi to the router, I'd gladly do that.
Thanks for any help you can provide me with. I greatly appreciate it.
Have a great day.
Patrick.
P.S. If there's anything more that you need, I'll gladly provide it.
DD-WRT-IPv6-Setup.JPG
Description:
IPv6 configuration
Filesize:
53.83 KB
Viewed:
7182 Time(s)
Last edited by PatrickDickey52761 on Sat May 30, 2015 14:33; edited 1 time in total
Thanks for the reply (and the knock upside the head ). I used your thread, but was tired at the time apparently, because I didn't see my screen like yours or something. LOL
Two quick questions though. Do I need anything in the radvd.conf below all of this? And do I need anything in my startup besides the nvram lines (which are meant to keep it from flashing back to the Linksys firmware, if I understand correctly)?
------------ Update ---------------------
I made the changes as per your post. Then I removed the customized radvd.conf information, and the startup commands. Applied my settings. Now, in the upper right hand corner, it shows WAN IPv4: 67.7.22.15 IPv6: 2001:470:1f10:830::2, but when I go to www.whatismyipv6.com or www.test-ipv6.com, it still only shows my IPv4 information (and fails all of the tests). I did an ipconfig /renew on my computer, and it still has the 2001:470:1f11:... address (instead of the 1f10 address).
So, I'm closer, but not quite there. Now my question is, do I need to reboot everything? Also, do I need to disable radvd and radvd custom?
Thanks again. If this works, I owe you a beer or two at least.
Patrick.
Note the MTU is 1447, because my MTU is 1467 on my IPv4. So your MTU may be different.
I also had to add an echo statement to my startup. This is because my actual DHCP/DNS is provided by another device on my network--so I had to redirect the router there.
Hopefully this will help others (and myself if I have to do this again in the future).