NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Local IP connectivity to router apparently dead while WiFi still working
Hello, This morning our routing stopped working. WiFi still functions. I am not a networking amateur and have custom DHCP range and numerous fixed allocations set and so do not want to just reset the...
- Good sanity testing fundamentals, thank you, although I have fixed this. I believe that I have revealed what can be used to diagnose the exact problem in this upgrade.
Repeated resets, repeated FW upgrades to the latest all achieved nothing. But, I immediately restored settings everytime, as per sensible guidance here. It should not have been a problem, but it was. This 'restored' the problem that the firmware introduced. This begins to make the problem isolatable by Netgear.
So, I manually created my complex DHCP fixed structure and my SSID details. And it works now. Between devices and Orbi units. I should not have to do this.
This means that something in the configuration structure does not port well between these firmware versions. I presume it has something to do with routing/iptables that this new App Armor thing has poorly implemented, regardless of whether it is enabled(!) (I do and did not have it enabled).
None of this is good news. I have two ruined days. And I would be irrational to trust my Netgear equipment. The scenario if I were travelling would be worse. If you have a NAS, an inward VPN, CCTV, alarms, Ring doorbells, Arlo or are just a modern user, you cannot trust a system or manufacturer that will destroy your network whenever it wants.
I am furious.
Yes, I see that now. Strange problems.
I know my ISP uses the 192.168.1.x subnet, so I wouldn’t be able to use the example telnet commands as given. Bringing up the hardware using paper clip reset should work but as I’ve mentioned elsewhere before, have to login to management console to trigger the LAN subnet reassignment routine. NG will move to 10.0.0.x.
I know my ISP uses the 192.168.1.x subnet, so I wouldn’t be able to use the example telnet commands as given. Bringing up the hardware using paper clip reset should work but as I’ve mentioned elsewhere before, have to login to management console to trigger the LAN subnet reassignment routine. NG will move to 10.0.0.x.
192.168.1.1 might be inused by your ISP cable modem if Orbi is in AP mode. In that case, you can telnet into your Orbi with the IP provided by your ISP router, which should be 192.168.1.x. If you have both 192.168.1.1 and 10.0.0.x in your networks, then you have a configuration error.
SW_ wrote:192.168.1.1 might be inused by your ISP cable modem if Orbi is in AP mode. In that case, you can telnet into your Orbi with the IP provided by your ISP router, which should be 192.168.1.x. If you have both 192.168.1.1 and 10.0.0.x in your networks, then you have a configuration error.
The ISP gateway has its own router built in which uses the 192.168.1.x subnet. The Orbi is also running in router mode. See my signature.
Yes, you are right. Your are describing a Bridge (aka IP passthrough) setup, the modem/router acts as a bridge for your Orbi router.
In a Bridge setup, the simplest configuration would be to select a different subnet or the IP passthrough address for the Bridge, i.e., 10.0.0.x or 192.168.2.x. That way, you can still operate under default Orbi IP subnet and the above tests will work as is. Otherwise, you have to replace those 192.168.x.x with br0/brwan IP addresses.
Keeping 192.168.1.x subnet for Orbi will make life simpler in the long run because the Orbi can continue to use the default subnet, 192.168.1.x, normally after each reset. This will save you time since you don't have to change Orbi DHCP setup to pick a new subnet as a result of each Factory Reset. One less custom configuration to change or worry about.
Thank you for pointing that out.
- Right. The important thing to mention is the Orbi will properly detect this condition and make the change on its own, but only when connecting to the management console via web GUI.
As for why to do this at all, I don’t want another device touching my data traffic. Eventually when Fiber gets here I intend to bypass the gateway altogether. - Also in the spirit of simplicity and defaults, the host router suffers the same firmware issues and then some, so have to pick poison carefully. That’s why I don’t want to touch that thing any more than I have to.