NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 Port Forwarding Not Working
I'm trying to get a program called Fantasy Grounds working, and it requires port forwarding of port 1802. I've done this on the same ISP at other locations, and recently moved to a new place in the s...
I found the solution on another forum. This is definitely a bug in the firmware.
There is a low threshold on the static IP address it will allow forwarding to. I was at .78 which was too high. I put my static IP to .10, and then pointed the rule to my new static IP and it worked.
To test this I put my static up to .101 and adjusted the rule. It failed again. I put it back to .10, and it worked again.
> I have a set of google wifi routers, and took the Nighthawk off the
> network. After adding a port forwarding rule for 1802, to my internal
> IP, the test completed successfully.
How many routers, connected how, are/were involved in this disaster?
If you're cascading multiple routers, then you can expect to have
problems with port forwarding (on an inner router). A complete
equipment inventory with a list of what's connected to what would be
better than relying on advice from people who must guess your
configuration.
When the R7000 is in place (and not working as expected), what is its
WAN/Internet IP address? (The first two octets of what should be your
public IP address ("a.b" out of "a.b.c.d") will do, if you don't want to
reveal the whole thing.)
> I set my PC to a static IP address, and also set a reservation for it
> in the router interface to make sure nothing else gained that address
> and causes a conflict. (192.168.1.78 is the address)
It would be simpler either to reserve a dynamic address for the
server, or else give the server a static address outside the DHCP pool.
Configuring the same data in two places (which must agree) is asking for
trouble. Shrink the DHCP pool, if needed, to create some non-pool
address space, and then use it.
> So this is definitely the R7000, and something goofy going on with its
> port forwarding rules.
Perhaps, but evidence is still far from conclusive.
I found the solution on another forum. This is definitely a bug in the firmware.
There is a low threshold on the static IP address it will allow forwarding to. I was at .78 which was too high. I put my static IP to .10, and then pointed the rule to my new static IP and it worked.
To test this I put my static up to .101 and adjusted the rule. It failed again. I put it back to .10, and it worked again.
> I found the solution on another forum. [...]
_Where_?
> [...] There is a low threshold on the static IP address it will allow
> forwarding to. [...]
Perhaps, but I doubt it. What are the limits of your DHCP pool
(ADVANCED > Setup > LAN Setup : Starting IP Address, Ending IP Address)?
Netgear firmware has been observed with many incredible firmware
defects, so I can't say that this couldn't happen, but it does sound
very unlikely. One last resort would be a settings reset (and manual
reconfiguration), which might clear some obscure settings corruption.