NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
magoldsm1
Sep 08, 2020Aspirant
RBR850 Port Forwarding Broken, Possibly Due to NAT Loopback Broken
This is an update to a previous discussion. I've done extensive experimentation and I've attached a PDF with results.
TL;DR
Enabling port forwarding of HTTP to a target machine fails when accessing the public IP address from inside the local network. Running IIS on target machine (called TARGET). Testing access to server from 3 machines on internal network: WIRED, WIRELESS and TARGET. As one might guess, WIRED is connected via Ethernet to the LAN, WIRELESS is connected via Wi-Fi. TARGET is connected via Ethernet.
All machines can browse to http://192.168.1.25 (TARGET's local IP) correctly.
Only WIRELESS can browse to http://my.public.ip. WIRED and TARGET get timeouts.
If have tried other wired and wireless machines on my LAN. When accessing my public IP address, wired connections fail, while wireless connections succeed.
I also switched machine WIRELESS to Ethernet; it failed. However, switching machine TARGET to Wi-Fi still fails.
See the attached PDF for a discussion of additional symptoms and why I believe the problem may be related to NAT loopback.
Thanks,
Michael
1 Reply
- orbiraApprentice
You are right there is issues with NAT loopback due to the way packets are handled by IP tables.
I have been using
echo 0 > /proc/sys/net/bridge/bridge-nf-call-iptables
to workaround the issue. For details, please see the thread
https://community.netgear.com/t5/Orbi-AX/NAT-loopback-debugging-help-wanted/m-p/1972621#M7099
Hope this helps.