garycnew
Senior Member
All:
I've run into an issue on Asuswrt-Merlin 384.19 where creating a PortForward through Advance Settings > WAN > Virtual Server/PortForwarding creates the following iptables (but are not working):
A test OpenSSL s_client Connection is Refused.
If I bind the application directly to 198.91.69.78:443 instead of 192.168.0.1:8888 it works without issue.
I've confirmed that the destination application is listening on 192.168.0.1:8888, but for some reason the PortForward isn't bridging the Public IPort and Private:IPort.
Are there any known issues with Asuswrt-Merlin and PortForwarding?
Your assistance is greatly appreciated.
Respectfully,
Gary
I've run into an issue on Asuswrt-Merlin 384.19 where creating a PortForward through Advance Settings > WAN > Virtual Server/PortForwarding creates the following iptables (but are not working):
Code:
iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
iptables -A VSERVER -p tcp -m tcp --dport 443 -j DNAT --to-destination 192.168.0.1:8888
A test OpenSSL s_client Connection is Refused.
Code:
# openssl s_client -connect 198.91.60.78:443
connect: Connection refused
connect:errno=111
If I bind the application directly to 198.91.69.78:443 instead of 192.168.0.1:8888 it works without issue.
I've confirmed that the destination application is listening on 192.168.0.1:8888, but for some reason the PortForward isn't bridging the Public IPort and Private:IPort.
Are there any known issues with Asuswrt-Merlin and PortForwarding?
Your assistance is greatly appreciated.
Respectfully,
Gary