So radvd needs configured then.
I have radvd installed on my OpenWRT router, I don't imagine it is configured though.
I set the 'AdvManagedFlag' to '1' in the interface block to enable stateless auto configuration
config 'interface'
option 'interface' 'lan'
option 'AdvSendAdvert' '1'
option 'AdvManagedFlag' '1'
option 'AdvOtherConfigFlag' '0'
list 'client' ''
option 'ignore' '0'
To configure it I went into
/etc/config/radvd and found the following sections which I believe need to be configured to do what you are suggesting:
config 'prefix'
option 'interface' 'lan'
list 'prefix' '2001:470:20::2/64'
option 'AdvOnLink' '1'
option 'AdvAutonomous' '1'
option 'AdvRouterAddr' '0'
option 'ignore' '0'
config 'route'
option 'interface' 'lan'
list 'prefix' '2001:470:20::2/64'
option 'ignore' '0'
/etc/config/radvd -
config file docsBoth of the 'prefix' listings above I pulled from the
Routed IPv6 Prefixes in my tunnel configuration.
When I restart networking on my router I also get the message:
Cannot determine local IPv4 address for 6in4 tunnel henet - skipping
Configuration file: /var/run/hostapd-phy0.conf
The error appears
here, but it appears that the bug was a
duplicate that has since been fixed.
Now I get limited ipv6 connectivity on my Windows 7 box, it receives an IP address ala radvd and I can both ping and visit the ipv6 versions of facebook and google. For some reason I can't reach any of HE's websites on it, and after running a test on test-ipv6.com I think I know why, but I'm not sure I know what to do about it:

I would imagine I need to set an IPv6 compatible DNS up somewhere. But I think the larger problem that I need to solve first is what to do about those large packets that don't appear to be coming through.
I also clicked on the "Technical Info" tab, on test-ipv6.com and it offered the following suggestions for getting the failed tests to pass:
Test for Dault Stack DNS and large packet timeout (15.012s | Validates that you can connect ot a dual-stack server (like the ds test); and that you can send/receive large packets on that conneciton. If this test times out for any reason, it indicates trouble for World IPv6 Day. |
Test IPv6 large packet timeout (15.009s)
| Validates that IPv6 requests with large packets work. If this test times out, but other IPv6 tests work, it suggests that there may be many PMTUD issues; possibly involving IP tunnels. |
Test if your ISPs DNS server uses IPv6 bad (0.227s) | This is a test of your ISP's resolver (instead of a test of your host). If this test passes, your DNS server (often run my your ISP) is capable of reaching IPv6 DNS authoritative servers on the Internet. This is not critical (at this time) for you to reach sites via IPv6.. |
Not sure how to fix the issue with the large packets.
Also a little concerned about my security at this point...I have the firewall turned on, on my Windows 7 box, but I don't know what tool is the equivalent of good old fashion
ShieldsUp! other than something like nmap, but I imagine I'd have to leave my house to try that.