Hello,
My (AsusWRT-RMerlin 378.55) setup is such that I do not need NAT (the device acts as "router" rather than "gateway", though with firewall still enabled); consequently, I have disabled NAT in the general WAN settings.
Setting port "forwarding" (better said port "opening") when NAT is disabled does not work; in other words, nothing shows up in 'iptables -L -t filter'.
When NAT is disabled, one would expect for ad-hoc rules to appear in 'iptables -L -t filter' (firewall rules).
On the other hand, of course, nothing ought to appear (and actually doesn't) in 'iptables -L -t nat' (NAT rules).
Adding the 'iptables -L -t filter' rules by hand (firewall scripts) does solve the issue.
I don't know if this is the proper place to report such bug. Please correct me if not.
Also, I'm totally new to AsusWRT source code (on GitHub).
Where should I look for the web interface code ?
Where should I look for the code that translate "port forwarding" configuration into actual "iptables" commands ?
Thanks and best,
Cédric
My (AsusWRT-RMerlin 378.55) setup is such that I do not need NAT (the device acts as "router" rather than "gateway", though with firewall still enabled); consequently, I have disabled NAT in the general WAN settings.
Setting port "forwarding" (better said port "opening") when NAT is disabled does not work; in other words, nothing shows up in 'iptables -L -t filter'.
When NAT is disabled, one would expect for ad-hoc rules to appear in 'iptables -L -t filter' (firewall rules).
On the other hand, of course, nothing ought to appear (and actually doesn't) in 'iptables -L -t nat' (NAT rules).
Adding the 'iptables -L -t filter' rules by hand (firewall scripts) does solve the issue.
I don't know if this is the proper place to report such bug. Please correct me if not.
Also, I'm totally new to AsusWRT source code (on GitHub).
Where should I look for the web interface code ?
Where should I look for the code that translate "port forwarding" configuration into actual "iptables" commands ?
Thanks and best,
Cédric