Configuring pfSense to work with BT Infinity native IPv6

A quick post this one. I’ve been scouring the internet trying to find the right settings in order to connect up my pfSense to use BT Infinity’s native IPv6 implementation. Finally found the magic combination, which I’m sharing here for future reference, and hopefully help anyone else that might find this post.

Step 1: Configure your WAN interface’s IPv6 configuration type to be “DHCP6”. In the client configuration, check “Request a IPv6 prefix/information through the IPv4 connectivity link” and “Only request an IPv6 prefix, do not request an IPv6 address”. Set “DHCPv6 Prefix Delegation size” to “56”. Leave all other options as default.

Step 2: Configure your LAN interface’s IPv6 configuration to be “Track interface”. Scroll down, and under the “Track IPv6 Interface” section, select “WAN” from the IPv6 Interface dropdown. Leave “IPv6 Prefix ID” as default (0).

Step 3: Apply changes. And watch the interfaces status screen light up with that magic IPv6 address. RA will publish the prefix information out to your network shortly after connection, and your computer of choice should have an IPv6 address that’s useable.

Step 4 (optional): Reboot your pfSense box. If the interface doesn’t take the new addressing upon reconnecting, a reboot should do the trick.

That’s all! Surprisingly simple, really. It’s just finding that magic combination.

6 replies on “Configuring pfSense to work with BT Infinity native IPv6”

  1. This was just what I was looking for – thank you. I would just add Step 4: Reboot pfSense – that made it actually work. Cheers. MIke

  2. Hey Mike, thanks for the comment. I’ve updated the post. While I didn’t have to reboot the box in order to get it to take, I guess it’s plausible that if it’s got something else in memory, or some other weird configuration going it on it might not take immediately, thus rebooting would fix that all right up. Glad I could help!

  3. Yup, I’m stuck too.. those settings didn’t work for me either. GRR.. been driving me bonkers, about 6 fresh re-installs for pfSense 2.4.4 on Vmware ESXi. I can’t think for the life of me what’s going wrong.

Comments are closed.