Flint3 loopback NAT from Ethernet and DoH broken (bis)

[reaction359]

Hello,

Continuing the now closed topic on the subject, I see that the v4.9.0 beta release notes mention:

Improved the Port Forwarding feature to automatically perform one-to-one mapping for external and internal port ranges

Is this a workaround for the aforementioned issue? If not, any idea when this is going to be fixed?

Thanks!

cc: @bruce

[will.qiu]

Hi

This improvement means that when creating a new rule in Admin Panel > Security > Port Forwarding, the External Port and Internal Port fields are now automatically populated.

Regarding the Loopback NAT issue in Flint 3, please continue to use this temporary workaround:

(Flint 3) NAT loopback not working

Just an update: For those experiencing NAT hairpin/loopback issues, please try the following commands via SSH into the router to see whether they resolve the problem: sysctl -w net.bridge.bridge-nf-call-iptables=0 sysctl -w net.bridge.bridge-nf-call-ip6tables=0 If this resolves the issue, you can make the change persistent with: echo "net.bridge.bridge-nf-call-iptables=0 net.bridge.bridge-nf-call-ip6tables=0" >> /etc/sysctl.conf reboot Please note that if you adjust the network acceleratio…

Regarding the issue with DoH, could you provide more details?

[reaction359]

I was not aware of this workaround, the one I had been given in the thread I linked previously was “just create dns entries that point to your private IPs (therefore not going through NAT)”, which works in theory, except that we have many devices that use DOH and therefore don’t use the router’s DNS server, and it also requires extra permission from apps on iOS because they’re now seen as wanting to access the local network.

I will investigate your proposed workaround (and try to understand the compromise).

Thanks

[will.qiu]

Thank you for the clarification regarding the DoH issue.
It's good to know that the current workaround won't cause any problems with it.