So this snipp of a post I sent jschweitzer, figured I would post it here as well in case it might help someone else. He had asked for my help on the other board, I had not played with ipv6 much at all other than to disable it

I still don't really see much need for other than playing.. But to help him out I figured what the hell, I knew a bit about it - just never saw the need to run it on my home network and not doing anything with it at work, etc. So then I got side tracked with the certification thing

Got my sage level that afternoon, and chated with him a bit but then never got back to it - well last night I did, so put this together real quick today.
Its clearly prob the complete WRONG way to do it, or missing something, or extra somethings, etc. But it works! But Im really disappointed in the windows ipv6 stuff and no support for handing out dns with setup like this?? But now that my interest is peaked will get setup dhcpv6, etc. and caching nameserver that uses ipv6, etc. So anywhere hope this helps the next guy - and Please Please if someone has better way, or point out what I missed or shouldn't do or should, etc. Please POST!!! This is prob a hack at best - but it does work, have ran through it a few times. And I changed the actual info so be careful, maybe I typo'd something??
So Im going to setup dns on my tunnelbox, prob bind and looks like
http://klub.com.pl/dhcpv6/ will work on w7 box as well (says vista) If this is the case you can do everything with just w7 boxes on your network and a router that atleast supports forwarding protocol 41. (ie the router has to support getting the ipv6 through your ipv4 nat) But for now you can try this out, these are the commands I used that worked perfectly.
grab your tunnel info from HE
So mine is - changed a bit for privacy and to make a bit easier to read.
IPv6 Tunnel Endpoints
Server IPv4 address: 209.51.181.2
Server IPv6 address: 2001:470:
111A:b85::1/64
Client IPv4 address: 24.14.xx.xx
Client IPv6 address: 2001:470:
111A:b85::2/64
<-- tunnel endpoint on your w7 boxAvailable DNS Resolvers
Anycasted IPv6 Caching Nameserver: 2001:470:20::2
Anycasted IPv4 Caching Nameserver: 74.82.42.42
Routed IPv6 Prefixes and rDNS Delegations
Routed /48: Allocate /48
Routed /64: 2001:470:
111B:b85::/64
<--- Routed networkSo from that will need to create the tunnel boxes routed network IP address to assign to its local interface vs the linklocal address. So from that routed network are first client address would be
2001:470:
111B:b85::
1 <---- See the 1 added to the routed network.
Also you need to know the IPv4 address of your tunnel endpoint box, in my case 192.168.1.40 -- and you need to make sure your router forwards protocol 41 to this IP.. In my case a pfsense router, under advanced settings, network
IPv6 over IPv4 Tunneling - Enable IPv4 NAT encapsulation of IPv6 packets, IP 192.168.1.40
Also grab the w7 config items on bottom of page - keep in mind I changed a few items for privacy concerns. But you will be using some of these commands.
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 24.14.xx.xx 209.51.181.2
netsh interface ipv6 add address IP6Tunnel 2001:470:
111A:b85::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:
111A:b85::1
commands
---
#ok first thing clear out everything you might have done so, so from elevated prompt (run cmd as admin)
netsh int ipv6 delete interface IP6Tunnel
netsh int ipv6 reset
reboot
#make sure you don't have any ipv6 routes that you might have played with etc
route print
#do you see any ipv6 routes you might have entered with playing? Mine was clear
#So from elevated prompt (run cmd as admin)
#Lets drop into the netsh interface prompt so dont have to type those, etc.
netsh
interface
#just so sure teredo is disabled
teredo set state disabled
ipv6
# you should now see netsh interface ipv6> prompt
#So from the tunnelbrokers site for your tunnel on bottom of tunnel page you see your config options.
#first line is good - remember your behind a NAT so change the public IP they use to your private ipv4 of your tunnelbox, in mycase 192.168.1.40
add v6v4tunnel IP6Tunnel 192.168.1.40 209.51.181.2
add address IP6Tunnel 2001:470:
111A:b85::2
set interface IP6Tunnel forwarding=enabled
#now my local interface has been renamed to LAN, your prob default of "local connection" -- use what yours is called
set interface "Lan" forwarding=enabled advertise=enabled
#now here is where you add the first address of your routed network to your local interface - again mine is called LAN
add address "Lan" 2001:470:
111B:b85::1
#now adding this address should auto add your route - in my route table I see this
# 11 266 2001:470:
111B:b85::/64 On-link
#now here is where you set default route use the tunnel and next hop is server side of your tunnel
#So if you try and add the route you will get already exist - we just want to publish it.. So
set route 2001:470:
111B:b85::/64 "Lan" publish=yes
#now just set default
add route ::/0 IP6Tunnel 2001:470:
111A:b85::1 publish=yes
---
So now you should be able to fire up another w7 box and it will use your tunnel box to get to the internet.. I would suggest you set on your tunnelbox static HE provided ipv6 dns - so 2001:470:20::2
Go to
http://test-ipv6.com/# and you should be 10/10 on both ipv4 and ipv6 and all ready for ipv6 day

I have tested this a few times and works great - is it the only way, doubt it, is it the best way? Again doubt it, I might have sage level, but some of this have not really played much with ipv6 other than getting my sage level

but this is the way I got it to work after looking and looking for a simple writeup on allowing other windows machine behind a nat use the tunnel. Now hopefully I didn't typo anything while hiding my actual ipv6 segment. Remember if your putting in the exact numbers you see here for your ipv6 stuff its not going to work - these were mine and changed to make easy to see tunnel network vs routed network.
Now on your other clients you should see their ipv6 showing their on your routed network
IPv6 Address. . . . . . . . . . . : 2001:470:
111B:b85:748f:b64e:848:1943(Preferred)
Temporary IPv6 Address. . . . . . : 2001:470:
111B:b85:e44b:2cae:31db:64cd(Preferred)
Link-local IPv6 Address . . . . . : fe80::748f:b64e:848:1943%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.222(Preferred)
So you should see ::/0 route to your tunnelboxes local link
11 266 ::/0 fe80::fc2c:187c:aed5:a694
tunnelbox ip addresses
IPv6 Address. . . . . . . . . . . : 2001:470:
111B:b85::1(Preferred)
IPv6 Address. . . . . . . . . . . : 2001:470:
111B:b85:fc2c:187c:aed5:a694(Preferred)
Temporary IPv6 Address. . . . . . : 2001:470:
111B:b85:347c:f1b9:ef2a:7815(Preferred)
Link-local IPv6 Address . . . . . :
fe80::fc2c:187c:aed5:a694%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.40(Preferred)
So now just set your client box to use your HE dns.. Then go to the ipv6 test site and you should see
Your IPv6 address on the public internet appears to be 2001:470:
111B:b85:e44b:2cae:31db:64cd
Your IPv6 service appears to be: he.net or tunnelbroker.net
And
10/10 for your IPv6 stability and readiness, when publishers are forced to go IPv6 only
Hope that helps!!!