jaro3

The script /lib/netifd/proto/map.sh is from 2014 and is written for iptables not nftables that are used in 22.03 onward as default fw4. The interface doesn't come up... There are some...

Even the ipip tunneling of OpenWRT is useless since it only creates ip4-in-ip4 tunnels. fw3 should be made a dependency of map or adapt /lib/netifd/proto/map.sh for fw4....

There are patches for nftables to support RFC-7597 too (--psid option to masquerade). And the Kernel ipv4-in-ipv6 tunnel module....

Unfortunately I am not familiar with the json_ commands so I am writing own firewall.user script with nft and bring up the MAP-E interface using the ip-full commands from a...

I don't understand the "json_ language" but the expressions in the map.sh script are clearly iptables rather than nftables type: json_add_string target SNAT json_add_string target ACCEPT [ -z "$zone" ]...

this is diff between the old(working fw3) and new(fw4) system scripts: diff -uNr ota/lib/netifd/proto/map.sh ota_new/lib/netifd/proto/map.sh --- ota/lib/netifd/proto/map.sh 2021-01-23 13:42:14.000000000 +0900 +++ ota_new/lib/netifd/proto/map.sh 2023-01-23 12:43:07.000000000 +0900 @@ -25,30 +25,30 @@ local...

If it would be helpful I can post the ip commands to bring up the MAP interface with corresponding nftables script to perform the port range masquerade.... Will test it...

OK I will go there and replace the router and test it tonight... Do you also know how the map.sh or the calculator brings up the MAP interface, does it...

Even after the MAP interface has been brought up, there is still the issue with port masquerade. Do you know whether these patches have been included in the current version...

I will try tonight and report. Have to get home and cut the whole household from Internet to test... Is there any place e.g. under /tmp where the odhcp6c client...