IPv6 + HE tunnel –> interface subnet mask = 128
-
… Sorry but it seems you need a bit more play/study time before any sort of production use..
… and the good news is : HE.net has everything covered for you - they will actually really cover you !!
It starts here : http://he.net and click on : http://ipv6.he.net/certification and when done, use their "free" tunnel offer.
No more questions ^^ and a very original T-shirt for free. -
I am pretty sure there is an issue with the latsest version of pfSense (2.3.4). I cannot put my finger on it. At least not yet.
On my production firewall, I received the IPv6 from my provider using DHCPv6. I also got 128 subnet preventing anything to work. As I also owned a /48 from HE. I installed a second pfsense where I can play with at will using my production firewall to provide DHCPV6 and subnet delegation.
During all my test, I always got a 128 subnet on my test firewall (sniffing the network shows the correct /64 announcement). I try many different configuration without success. Sometimes if I used SLAAC on my test firewall it works fine (reconfiguring the main firewall accordingly) , switching to DHCPv6 seems to provide the correct result…
It is inconsistent and so far I could not create a test that provide each time the same results that would allow a good basis to fill a bug report...
I am still searching but this 128 subnet appears after I installed the latest release. My next step will be to install an older realease on my test firewall....I'll let you know the outcome.