Can't access port-forwarded/natted services from another local network
-
I have a network setup with three interfaces: LAN (192.168.50.0/24), WAN (Public IP), and DMZ (192.168.30.0/24). Traffic between the LAN and DMZ is completely blocked.
There is a service running on 192.168.30.11 using ports X and Y. I created port forwarding rules under Firewall -> NAT -> Port Forwarding that direct incoming traffic from the WAN interface to 192.168.30.11 on those specific ports.
The issue I'm facing is that my friend, who is on a different network, can access the service just fine. However, I am unable to access it from my LAN (192.168.50.2), even when I try using the public IP and the correct port (for example, Public-IP:Port).
I have a hunch that this might be related to NAT reflection or loopback, but I'm not entirely sure. I'd appreciate any guidance or suggestions on how to troubleshoot or fix this.
One of the rules:
-
@keijei said in Can't access port-forwarded/natted services from another local network:
suggestions on how to troubleshoot or fix this.
Just create a rule on your lan interface that allows access to the ports and the 192.168.30.11 IP.
There is little reason to do a nat reflection.
-
@johnpoz I was thinking about doing this, but I was unsure if it was the right way to go or if it was the "lazy, easy, not-so-safe" way. Thank you for the advice.
-
@keijei It is the correct way, why would anyone want to bounce off the wan just to be forwarded back into the local side.. Makes zero sense.
Like wanting to go to the bathroom from the living room - but hey let me go to the front door of the house first.
-
@johnpoz I see, thanks for explaining and the help!
