New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#3875 - NAT reflection/loopback fails with multiple zones #8868
Comments
KiralyCraft: I can confirm this is indeed something we need. I stumbled across this issue too and I'm now trying to work around it with iptables, it will be messy though |
For anyone coming across this now, the formatting got messed up on this issue thread #7950 when the bug tracker was migrated. The below works for me added via LuCI 'Firewall - Custom Rules' page. It works for other services too, just modify the port numbers. These rules are in addition to the "port forward" rule for the one VLAN you set.
|
Any benevolent soul that can show me how to do this with nftables in 22.03? |
My current workaround for fw4 is to create a hotplug script that updates a custom nft rules file when the WAN address changes. It's not ideal because it's writing to the storage, but I haven't found any way of making use of the WAN address from within the nft file (it'd be great if fw4 defined a variable for it).
|
Hmm, both current versions of fw3 and fw4 support Example:
|
Thanks! somehow I missed it. I've tested it and works as expected, so I guess that this issue can be closed. |
Closing this because support has been implemented a while ago. |
phqzgunsfjror:
I just want to reopen the ticket because it was closed (reason EOL of the version where it was created).
It it not a bug but would be a nice feature for everyone who hosts private servers.
Everything can be found here:
https://bugs.openwrt.org/index.php?do=details&task_id=1645&dev=4
The text was updated successfully, but these errors were encountered: