IPv6 on pfSense vs others



  • So a couple of things I've noticed about pfSense's IPv6 implementation compared to other routers' - and I include a number of open-source firmwares in that…

    1. If you use DHCPv6+PD on the WAN, pfSense does not allow setting a "static" (I use quotes because technically the prefix could change) LAN IPv6 address for the router. Other router firmwares allow you to set the host portion of the IPv6 address that the router will use (I would usually use [prefix]::1), and then the router applies whatever prefix is designated by the ISP. Is there some reason that pfSense doesn't permit this?

    2. Is there a reason that pfSense doesn't register its own LAN IPv6 address in the local DNS [forwarder|resolver] when it does register its IPv4 address? For example, I can ping gw and it will resolve to my pfSense box's LAN IPv4 address. But ping6 gw doesn't resolve. I know other routers do this also.



  • I noticed this myself… They both would come in handy... I would prefer to use [prefix]::1 for my router LAN interface also…
    With TWC service, I was able to statically setup DHCPv6 using the prefix I already knew but removed it since it could change and if it did; my IPv6 connections would be dead until I manually update the box with the new prefix.



  • And that's something else I've seen in some of the other routers/firmwares… DHCPv6 is also still available in those setups. However, they don't exclusively use DHCPv6... most of them don't even let you change the type of RA that is sent... they hard-set to "Assisted", so that SLAAC-only devices (like Android) still function. But everything I have on my network is capable of using DHCPv6, so I'd much prefer to use that as well.



  • Its all there under the hood to make it happen I believe. The Web GUI needs to be updated/modify to allow the different IPv6 configurations to be generated.


Log in to reply