I've been enjoying the end to end connectivity I get with IPv6.  For many home networkers, this will be best method of doing a home network.  Just get IPv6 and you have plenty of space for a place on the web!  I have setup a Linux based IPv6 router and a subnet just for the Internet facing servers.  I could filter this subnet out at the router so it can't connect to the hom LAN.  However, I have just begun and have much work to do.

You can view my notes at azcrumpty.mooo.com/, which only works if you have IPv6 setup and working.  If you don't, you may use a gateway azcrumpty.mooo.com.ipv4.sixxs.org/.

My ISP doesn't block the smtp port, 25 on IPv6, so I can run my own mail gateway.  If your provider can send to IPv6, which I find many don't, you can email me at email at ipv6@azcrumpty.mooo.com.  The folks at FreeDNS have graciously allowed my to piggyback on their domain.

I will take this server offline after about a month since the computer it runs on is actually my Linux Mint laptop, which I would like to use for laptop use. It is virtualized, so I can move it should I wish to keep it turned on.

Dual IPv6 Networks In Home GatewayI have completed adding IPv6 to my home network using both 6in4 and 6to4 transition methods.  The IPv6 guide at the DD-WRT site covers everything you need, but I had one question after I completed 6to4.  Could I add multiple IPv6 network providers?  The answer is yes, and it is very easy to do.  Breaking with the spirit of end to end networking, I decided I wanted my guest network IPv6 network separated from my main network.  This is not necessary with the big /64 network you get from the providers, but I wanted to try it out since I like having a network that I can use to look from the outside in.  Teredo Tunneling is the most painless way to IPv6, but it was the slowest method of using IPv6.

The changes were simple enough, only needing the user to setup the second tunnel using the tunnel provider's instructions and a unique name.  Basically, the router advertisement daemon's config files needed to be changed to announce the 6to4's network, 2002: on the guest interface br1.  The 6to4 start script needed the -p option used to specify a new pid file for the second daemon.  I used the command watch 'netstat -an | grep tcp6 to see what network connections were using IPv6.

The home network uses the 2001:132:d:28a network provided by Hurricane Electric. The radvd.he.conf file only needed to be configured to announce the 2001:132:d:28a::/64 prefix and the start script is the same one you would fine on the DD-WRT IPv6 site.  On starup, the router's route tables and interfaces show the correct settings for the internal interface br0 and the external interface br1. Again, watching the netstat output showed plenty of IPv6 connections.

Both networks checked out with the IPv6 test site.  A tertiary option is to use Teredo tunneling on a host behind another NAT in my my home network which gives me a third network to work with.
 
I put the IPv6 startup scripts into Optware script format along with the config files for radvd.  I do the ipv6 insmod command in the DD-WRT startup.   

So now, my home network has all the benefits of a node having full end to end connectivity with no more pesky NAT preventing me from publishing my own content or directly communicating with another peer on the Internet.  But also note that configuration is completely unnecessary since I have 2^64 addresses available for use and could have divided my block up for each segment.  One radvd process can advertise to both interfaces and the two networks can be part of the same /64.  All I had to do was add an interface address in the block to br1 and the two become connected, but that seemed like normal networking.