Project

General

Profile

Actions

Feature #11901

closed

Add MAP-T/MAP-E support to pfSense

Added by Kent Morwath about 3 years ago. Updated about 3 years ago.

Status:
Needs Patch
Priority:
Normal
Assignee:
-
Category:
Interfaces
Target version:
-
Start date:
05/10/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

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.

Actions

Also available in: Atom PDF