-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add MAP-T/MAP-E support #4983
Comments
This issue has been automatically timed-out (after 180 days of inactivity). For more information about the policies for this repository, If someone wants to step up and work on this issue, |
Even Iliad (Free) with the new internet offer via FTTH will also use the same protocols |
Any news on this issue? I would like to contribute but I don't even know where to start |
No news. pf.conf(5) holds a feature here:
I suppose it would have to be added to 1:1 rules? The original ticket is a bit light on the requirements part. We can offer what pf(4) offers, but if that is enough here has not been established and how it should be configured from the GUI... |
Besides MAP-T/MAP-E support, it's not clear to me if "standard" ipip6 (i.e. with manual parameters instead of being provided by DHCPv6) is supported in opnsense... |
Let me share about the situation in Japan. As far as I know, some Japanese users who are building routers on FreeBSD or OpenBSD are using map-e-portset to connect. https://qiita.com/yshdsnd/items/f8fb7ed136c19092b538 I found someone patching the kernel to connect with MAP-E. Wow! |
Is there anyway to implement this inside opnsense? https://github.com/toru-mano/openbsd-pf-map-e-ce |
unlikely, best check |
I think Japan users (such as myself) are still interested in this. Seems someone got things working as needed for OpenWRT: https://github.com/fakemanhk/openwrt-jp-ipoe Maybe that could act as a guide for OPNsense? I haven't tried yet, but it sounds like the |
Well, same comment #4983 (comment) still applies, if someone wants to investigate how this can work on bsd, the starting point is implementing what's described in |
I'll get testing! |
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
No
Describe the solution you like
Please add MAP-T and other transitional technologies support as soon as possible.
Additional context
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 using from a dual stack implementation used till now to a IPv6 + MAP-T network from August 2021. Melita (another ISP in EUROPE) is already using MAP-T. Looks like that Japan ISPs are heavily depending on MAP-T. 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.
Right now there little to nothing CPEs capable to do so. The only open solution so far is Openwrt. Without MAP-T support, OPNsense won't be able to obtain a IPv4 address and access IPv4-only destinations.
The text was updated successfully, but these errors were encountered: