On Thu, Dec 9, 2010 at 8:48 AM, Joakim Aronius <[email protected]> wrote:
> Hi Jeff, > > As Stuart and Simon pointed out, this is not how you should do it. You need > to get a bigger slice e.g. /56 from your provider to subnet your internal > network with. Your /64 should only be used on the network between your > operators GW and your GW. > > Alternatives: > 1. Get a /56 from Comcast > 2. Get a tunnel from sixxs or HE (which will assign you a /56) > > It might also be possible to run your GW in bridged mode, havn't tried that > myself though. > > Comcast probably assumes that you should put all your gear on the network > without a GW.. > > Jaokim, I agree with all that you have said, this makes sense in all terms of networking. But I had to disregard some of my IPv4 knowledge to get this working. Thanks to the suggestions of others on-list who emailed me off-list I was able to get it working (while ignoring what I considered to be proper network topology): The current solution: I assigned 2001:55c:dead:beef::2/64 to my vr1 internal LAN interface. (This seems odd, but perhaps is due to my lack of knowledge around ipv6 subnetting. How can I just assign a ::2 address on a different physical network, while that same network is used on the interface between my ISP and my GW's internet-facing tunnel?) This provided my internal machines with a next-hop gateway to get out to the IPv6 Internet. After doing this and restarting rtadvd, my internal machines now have ipv6 connectivity. Thanks to all who have responded on and off list, hopefully as I gain more expertise with ipv6 I can start contributing code to the project. Cheers, Jeffrey
