Jeroen -- Thank you for your reply:-) You are correct in that all xxxx's are the same value. I also had suspicious that this may be an issue with my setup but I'm still trying to wrap my head around ipv6 here. Lets try to clarify a few things. Perhaps I am just misunderstanding something simple with ipv6. In ipv4, I would use iptables/MASQUERADE to set up a NAT to share my ISP provided ipv4 IP to my home network. On to ipv6, the use of NAT/MASQUERADING is not necessary as I am provided a /64 ipv6 address from my ISP (or in this case, SixXS). The first 64 bits should be the routing information to direct the ipv6 traffic to my router. Then I can use radvd to auto-configure my home network ipv6 IPs using the last 64 bits of my ipv6/64 address on the router. Thus, an example client on my network will have the ipv6 address of (based upon the client's mac address): inet6 2001:4978:xxxx:xxxx:226:8ff:feec:4407 prefixlen 64 tentative autoconf Therefore, the /64 prefix will direct traffic to my router, then the router will route the traffic to the client on my network based upon the last 64 bits of the ipv6 IP above. This is also why I have the ::3 IP on eth1 is showing as a /128 - it will serve as the gateway for incoming ipv6 traffic on eth1 and be forwarded out on sixxs/eth0. I performed a wireshark capture on eth0 (the interface with a static ipv4 through which the sixxs interface is tunneled through). When I ping an external ipv6 addresses (i.e. ipv6.google.com) from a client, I see outgoing echo requests in Wireshark on the eth0 interface, however the incoming echo replies are not showing on the eth0 or sixxs interfaces - leading me to believe that the ipv6 ping is leaving my home network but not returning. I understand that I can request a /48 subnet which would allow me greater flexibility. However, my tunnel needs to exist for a few weeks longer to generate the required points to do this. However, based upon my understanding, I should be able to create a network of clients based upon a single /64 ipv6 address. If it still matters (granted I should adjust the ipv6 MTU for performance...): root@rocket:~$ ip -6 ro show 2001:4978:xxxx:xxxx::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 2001:4978:xxxx:xxxx::3 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2000::/3 via 2001:4978:xxxx:xxxx::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295 fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 default via 2001:4978:xxxx:xxxx::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295