NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
znypar
Feb 02, 2016Aspirant
R7000 port forwarding not working while modem is in bridged mode
Hi guys, I have a R7000 wired directly to my NVG589 modem, which is running in bridged mode. It seems I am unable to forward any ports to servers I have running behind the router. (My primary goal ...
- Feb 05, 2016
Thanks for responding rpoffen,
I did make sure to enable bridge mode (well, not true bridge, but IP passthrough).
The R7000 was listing the public IP as NAT address.
SO, I think I just stumbled on the cause. And it's a little bit embarrasing, but hopefully it will click for someone who changes their network structure like I did.
On the server machine, I had manually assigned the IP, subnet, and gateway within the network adapter settings, due to limitations within the modem for its routing config. When the topology changed, so did the gateway address, of course. I'm not sure how, but I had internet from within the machine for a time and also was able to access the machine from within the local network via the public IP in addition to its local IP (as explained before), so the IP was likely still passing through the modem's gateway... (for learning, I would be interested in someone explaining how this worked for a time)
Prior topology: connection to the outside is: Modem -> POE switch -> (everything else, and router as access point)
Current topology: connection to the outside is: Modem -> Router -> POE switch -> everything else
Anyways, I assigned a static IP from within the R7000 for the server, set the server to automatic, and now things are solid and functioning as hoped.
TLDR; Check your machine configuration, it might be conflicting with the router. If you're trying to port forward to a specific machine and it isn't working, try forwarding to a different machine.
znypar
Feb 03, 2016Aspirant
I wanted to clarify that the port forwarding was only configured AFTER the firmware update. No port forwarding was configured before the update (as the changelog suggests to reconfigure).
Also that a factory reset was performed after the firmware update.
- znyparFeb 03, 2016Aspirant
To continue to track this issue for the benefit of others:
The port forwarding works correctly while within the internal network and using the external IP (99.xx.xx.xx:8081).
The forwarding still does not respond from an external network using the external IP.
- rpoffenFeb 04, 2016Virtuoso
Perhaps the modem is not fully in bridge mode. On another thread the user had to uncheck the NAT function in the modem setup as well as enable bridge mode.
What IP address does the R7000 get on its WAN port?
- znyparFeb 05, 2016Aspirant
Thanks for responding rpoffen,
I did make sure to enable bridge mode (well, not true bridge, but IP passthrough).
The R7000 was listing the public IP as NAT address.
SO, I think I just stumbled on the cause. And it's a little bit embarrasing, but hopefully it will click for someone who changes their network structure like I did.
On the server machine, I had manually assigned the IP, subnet, and gateway within the network adapter settings, due to limitations within the modem for its routing config. When the topology changed, so did the gateway address, of course. I'm not sure how, but I had internet from within the machine for a time and also was able to access the machine from within the local network via the public IP in addition to its local IP (as explained before), so the IP was likely still passing through the modem's gateway... (for learning, I would be interested in someone explaining how this worked for a time)
Prior topology: connection to the outside is: Modem -> POE switch -> (everything else, and router as access point)
Current topology: connection to the outside is: Modem -> Router -> POE switch -> everything else
Anyways, I assigned a static IP from within the R7000 for the server, set the server to automatic, and now things are solid and functioning as hoped.
TLDR; Check your machine configuration, it might be conflicting with the router. If you're trying to port forward to a specific machine and it isn't working, try forwarding to a different machine.