Feature #11901
closed
Add MAP-T/MAP-E support to pfSense
0%
Description
The depletion of IPv4 addresses is forcing many ISPs, especially new ones, to migrate to IPv6 networks while supporting IPv4 using transition mechanism built on IPv6 (IPv4aaS - IPv4 as a Service), like MAP-T, MAP-E, 464XLAT and others (see RFC8585). Fibre and FTTH-GPON deployments are accelerating this changes, as new ISPs are entering the market but can't source IPv4 blocks large enough, and IPv6 based transition technologies are more appealing than IPv4-based ones like a dual stack with CG-NAT.
In Europe, Sky Italia (Comcast owned) will switch from a dual stack implementation used till now to a IPv6 + MAP-T network from August 2021. Others may follow, especially local ISPs offering specific services for the SMB market. Italy is a country where users have a right to use their own CPEs regardless of what the ISP provides - but the CPE must be able to comply with common standards used by the ISP network. Without MAP-T support, pfSense won't be able to obtain a IPv4 address and access IPv4-only destinations.
Please add MAP-T and other transitional technologies support as soon as possible.
Updated by Jim Pingle almost 3 years ago
- Status changed from New to Needs Patch
Unlikely this would come to pfSense since AFAIK there isn't any implementation of MAP for FreeBSD/pf. If someone wants to create one, then perhaps it could be considered.
TNSR supports MAP, however it can only act as a BR and not a CE.
Updated by Kent Morwath almost 3 years ago
I fully understand the lack of upstream support. Right now MAP- CPE support is very rare - one of the very few implementations I'm aware of is from the OpenWRT project. Don't know if it could be ported to pfSense, and with what effort. Another Linux implementation is Jool (https://github.com/NICMx/Jool)
As I had many people asking about pfSense support, at least this entry will track the status inside the pfSense project - thank you.