Hi. extremely new here and hope to get along well with everyone~
Unfortunate news, Japan uses a ipv6 transition protocol called MAP-E which is very minimally used through the rest of the world over 6rd/SIIT/NAT64+DNS64/MAP-T/DSLite.
Japan ISPs has decided to go with MAP-E which honestly is great on paper but there are issues that's come along with the very minimally used protocol in this environment as it isn't exactly supported well on OPNsense/PFsense with lack of documentation on getting it setup however it does appear to be available on FreeBSD.
I was wondering if it'd ever be possible or.. even a tutorial to figure out how to get this protocol to work on an OPNsense device.
I'm really looking forward to the talented individuals I've seen on this forum, I do have all the necessary info due to the map-e calculator (http://ipv4.web.fc2.com/map-e.html) to setup the map-e ~properly~
There is a github page (https://github.com/fakemanhk/openwrt-jp-ipoe) made by a talented individual named FakemanHK, however it's for openwrt.
is there any possibility to get this to be utilized on OPNsense.
or any guidance to force it to be used on opnsense [freebsd(opnsense/pfsense) related FW/Routers appear to be 20ms faster than openwrt somehow even with the IDS running]
Love you guys <3
Maybe look into this ticket it has recent activity with what looks like a possible solution.
https://github.com/opnsense/core/issues/4983
Quote from: Monviech (Cedrik) on May 01, 2025, 05:17:39 PMMaybe look into this ticket it has recent activity with what looks like a possible solution.
https://github.com/opnsense/core/issues/4983
I have read through and have tried to do various of the instructions(by Schmitmd as the gif device was also suggested inside a link by Shuntalto) a couple months ago however at the time wouldn't work as some stuff required ipv4 to connect (and without native map-e support i wasn't able to do anything as I wasn't provided with a pppoe so unfortunately i can't verify if this can~ work)
With the GIF device it appeared to just not associate with the BR device, as far as I could understand is that it would need to be natively implemented to opnsense to make more progress [under 25.1.5~] So I essentially had an ipv6 only network that appeared to not work with any shape way or form of DNS64 for some reason.
Expect user error as its 99% something i messed up, I'm currently not running opnsense so I can't check to see if it'd work at this point in time however.
Hopefully the developers find the time to enable/Allow map-e/map-t to exist without major modifications and potential bricking of devices currently.
(I'd rather not spend 5+ hours to get everything to work as expected to find out that... an update broke something somehow I am unfortunately not very capable with modifying opnsense)
I truly hope the developers check out the links provided by Shuntalto as it seems to even fix some issues natively included with map-e based off what I vaguely understand and experience on this network~
Thank you for the quick reply I really appreciate it