Ok here's the deal, I have IPv6 setup on my 3500L router running tomato. After screwing around with DD-WRT and getting problems from end ot the other I decided to try Tomato with it's nice GUI interface to IPv6. So now I have IPv6 setup on the router and it's working great from the router. I can ping IPv6 addresses and everything. My clients seem to be getting IPv6 addresses assigned, but I can't use IPv6 sites. ipv6-test.com says:
| Your IPv4 address on the public Internet appears to be *.*.*.* |
|
|
No IPv6 address detected [more info] |
|
|
When a publisher offers both IPv4 and IPv6, your browser appears to be happy to take the IPv4 site without delay. |
|
|
Connections to IPv6-only sites are timing out. Any web site that is IPv6 only, will appear to be down to you. |
|
|
Your DNS server (possibly run by your ISP) appears to have IPv6 Internet access. |
Now my ISP does not support IPv6 yet so the DNS is coming from the routers setup. Why can't my clients connect? I read something about IPv6 port forwarding, but I have no idea what to forward. I tried a wild card forward (* in the address lines) to pass all traffic, but the GUI won't accept that as an address. What do I do to get world access to IPv6 safely (meaning I want some protection from snooping ISPs, Gov and MPAA)?
I was looking at my routing table and I noticed this:
Destination Gateway / Next Hop Subnet Mask Metric Interface
default * 0 1024 v6in4
Somehow I don't think my default route should be on the v6in4 interface...
If I manually add my routed /64 to dev br0 then I my global IPv6 address gets out.
ip -6 addr add routed/64 dev br0
ip -6 route add routed/64 dev br0
Running those gives me the ability to get out, but I still don't get dns services. Keep in mind from my router I have everything, it's from my client machines I have issues. I wonder if there's a way to somehow bind v6in4 to br0?
Nothing? Nobody has any clue? This is really ridiculous. I've posted to the tomato forums and at least received some kind of response. Unfortunately still nothing that looks like a fix or solution.
Fixed it. For future reference just leave the Router IPv6 Address at default.