Is this script still needed on OpenWrt 24.10?

[missing233]

On my tests with the original OpenWrt map.sh in version 24.10, I could no longer reproduce the issue.
Ping works normally, and the Nichiban Benchmark also passes.
Is this script still necessary on current OpenWrt releases?

[fakemanhk]

These few months I am quite busy so haven't got time to check the behavior of 24.10.x, I'll setup a new one in coming 2 weeks and try.

But do you compared the map.sh, is it still same as stock one in v23? If yes that means on v22/v23 OpenWrt doesn't working correctly with MAP package.

[missing233]

These few months I am quite busy so haven't got time to check the behavior of 24.10.x, I'll setup a new one in coming 2 weeks and try.

But do you compared the map.sh, is it still same as stock one in v23? If yes that means on v22/v23 OpenWrt doesn't working correctly with MAP package.

map.sh hasn’t changed.
I remember someone said installing iptables-mod-ipopt was the key. I do have it on my router, but not sure if that’s what actually fixed the issue.

[xelxebar]

FWIW, I'm on TurrisOS (based on 24.10) and needed to install the modified map.sh. I also appear to have iptables-mod-ipopt installed. If I'm able to compare port group usage stats between the different map.sh files, I'll share here.

[missing233]

FWIW, I'm on TurrisOS (based on 24.10) and needed to install the modified map.sh. I also appear to have iptables-mod-ipopt installed. If I'm able to compare port group usage stats between the different map.sh files, I'll share here.

I’m not really familiar with Turris OS.
Do you know if its firewall is fw3 or fw4? maybe the behavior differs between nftables and iptables.

[xelxebar]

Do you know if its firewall is fw3 or fw4? maybe the behavior differs between nftables and iptables.

Ah, good observation. Looks like I'm on fw4, which apparently is the default for 22.03+.

[cmspam]

With a default install of 24.10 the issue persists for me, and the new file is needed.