NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dlcrow
Sep 14, 2026Aspirant
RBE970/RBE971 Routing Issues
I have an Orbi RBE970/RBE971 mesh environment that was set to auto-upgrade, but I noticed it was still running 9.12.4.16 even though the firmware update page said that upgrades were available. I used...
dlcrow
Sep 29, 2026Aspirant
Well, I figured it out. Quite by accident.
While re-IP'ing and reverting the re-IP'ing seemed to make more things work, I just now realized that the process of doing that messed up the Port Forwarding tables. The internal start port and internal IP address were changed. Originally, they looked like
HTTPS 443 443 $A.1
I didn't check to see what it looked like when I re-IP'd to 192.168.1.x/24. But after putting the network back to 172.29.x.x/24 ($A), all of the port forwarding entries looked ike
HTTPS 443 172 $A.172
For all the port forwards that are a direct port match (e.g. internet port 443 to internal port 443), connections from the non-destination hairpinning to the destination (e.g. $A.138 to $B which ends up at $A.1) work just fine. But connections from $A.1 to $B which ends up at $A.1 do not.
And I don't expose my SSH to the internet on port 22, but instead on another random port. So my configuration looks like
SSH ALT <randomport> 22 $A.1
As soon as I fixed the SSH line to look like the above from the incorrect one that had an internal start port of 172, the internal SSH connections appear to come from the internet. And as soon as I delete the SSH forwarding line, it goes back.
So, it is the port forwarding that is messing with the connection paths.
FURRYe38
Oct 15, 2026Guru - Experienced User
Glad you got it working. Please mark your thread as solved so others will know. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
Enjoy. 📡