Ahhh, i missed part of that... Right, so looking at the requirements, i have a follow up question:
in requirements it says: To setup Multi-WAN for IPv6 the following items are needed: * Two WANs, and IPv6 connectivity setup on both. * Gateways added to System > Routing for both, and confirmed connectivity on both. * LAN using a static routed /64 or similar * A routed /64 or larger block available on both WANs Part one can be done using the tunnel broker setup guide, and part 2 will be done after... 4 is also part of the tunnel broker, but that gives me a /64 or /48 for each WAN link (3 in my case). How do i get this static routed /64? is that something i get from HE.NET or something i make up (like a 192.168.X.X address?). is it possible to have an IPv6 block that can be reached though any of the WAN links (say, again, random numbers used here) Say WAN 1 has an IPv6 address of 2001:470:100:100::1/64, WAN 2 is 200:200 and WAN3 is 300:300... and LAN is 400:400... would the 400:400 block be publicly route-able via 100, 200 or 300, or is that just something that can be done with BGP? If its not possible with a home connection, so be it, just asking the stupid questions so you don't have to! :) --Tiernan ________________________________________ From: List <[email protected]> on behalf of Jim Pingle <[email protected]> Sent: 09 March 2015 14:54 To: pfSense Support and Discussion Mailing List Subject: Re: [pfSense] Multi WAN IPv6 On 03/09/2015 10:28 AM, Tiernan OToole wrote: > But there is a problem... The Multi-WAN one assumes that both WAN > connections give IPv6 addresses, which in my case is false, and the > Tunnel Broker assumes you have one WAN connection... Last time i tried > this, mind you with a different router, all traffic went though one > connection (the one the tunnel broker knew about) and nothing went > though the rest... > > > Any one done this before? Actually the instructions were written with a separate tunnel broker connection on each WAN. Though it may work with one tunnel broker and using a gateway group on the tunnel endpoint update dyndns entry, I'm not sure anyone has tried that. Jim _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
