Hi,
I bought a Turris Ominia 2020 model RTROM01-FCC then I connected the router to a MAP-T line.
After installing map-t module, I am able to take MAP-T ipv6 from the BNG and surf using this protocol, but the IPv4 is not calculated so I can’t surf in IPv4.
Because using a third party router installing Openwrt version 21.02.1 r16325-88151b8303 on, for example a TP-Link 1750ac v2/v5, I am able to surf both in IPv6 and IPv4, could you help me to understand why with Turris I can’t surf in ipv4?
The current Turris version I’m using is TurrisOS 5.2.7 9882a54c4848e2e282bca435c6aa0025d9fa37df.
I don’t know these kinds of deployment, really. I assume that you’re missing the DNS64 part, i.e. generation of fake AAAA records in DNS in cases where only A exists? (and perhaps also some other parts which I most likely don’t know at all?)
Well, if it works… can you please send us some screenshots, how does it even look?
You know, no ISP here in Czechia provides MAP-T so we have no idea what does it mean and how does it work.
Here you can find all specs RFC 7599 - Mapping of Address and Port using Translation (MAP-T) from IETF of MAP-T.
Basically starting from an IPv6, the BNG sends all information and the starting address of IPv4 pool to calculate the Public IPv4 of the customer. It is usually used to share the same IPv4 between a range of customers.
Below there is the screen of interface after installing the MAP packet from System Software package.
I noticed that, even if from Openwrt it seems working and we are able to surf on internet, from the Reforis interface the ipv4 connectivity is down but I am able to surf and ping as you can see in the next post.