NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
Does this happen when using the default 192.168.1.1 subnet?
There is newer FW up as well:
New - RBE970 Series v12.1.11.15 Firmware Release - WW Region | NETGEAR Communities
Sorry for the delay in engagement. It took a while before I had the time to re-IP my network.
I am running the 12.1.11.15 firmware. The auto-updated didn't take me all the way there, but when I started having issues on 12.1.10.12, I manually updated to 12.1.11.15.
And now for something strange ...
I re-IP'd to 192.168.1.0/24 and kept all the host addresses the same (most are static IP assignments, but some are DHCP serviced by $A.1 - I don't use the Orbi DHCP server). I saw no change in behavior.
But after putting everything back to the 172.29.x.x/24 network, internal network connections all show as coming from internal hosts and not the internet host. The hairpinning still doesn't work with a "network is unreachable" message from a telnet client, but I'm happier to live with that than remove all the host- and service-based configuration that restricts network connections to my internal networks.
I even powered everything off (laptops, VMware server, Orbi router and remotes) and let it settle for a while. And I'm still in the spot of internal routing seeming to stay internal.
I am good with this state for now. Thanks for the guidance!
Interestingly, I just realized that while network connections (HTTP, HTTPS, SMTP, etc.) do not work from an internal host to my internet IP address, ping/traceroute do.