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.
Testyblahblah wrote:
>> Factory reset done and backed up settings reimported...
Just curious, have you tried testing with the 'Default' config instread of reimported your current configs after a Factory Reset?
If you are really running out of option, give it a shot and see if it makes a difference or not. Please power cycle your clients/devices before these tests with the Orbit Default config.
At your Orbi telnet terminal, please try these:
1. route (this should show two interfaces: br0 and brwan)
2. ifconfig br0 (check for error)
3. ifconfig brwan (check for error)
4. ping IP address of br0, which should be 192.168.1.1
5. ping IP address of brwan, which is from your ISP
6. traceroute IP address of br0: 192.168.1.1
7. traceroute IP address of brwan
8. nslookup orbilogin.com
9. ping orbilogin.com
Go to a Window 10 box:
1. tracert IP address of br0: 192.168.1.1
2. tracert IP address of brwan
3. ping IP address of br0: 192.168.1.1
4. ping IP address of brwan
5. nslookup orbilogin.com
6. ping orbilogin.com
Last:
- tracert 192.168.1.x (x is the IP address of the working and non-working devices)
Circle back with the results.
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.
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.
- Thanks to all in the community. No thanks to Netgear.
It was not clear in my thanks and recent replies who was being thanked. It all jumbled up and didn't make sense for you - I assumed it would quote/tag you, but didn't. >> This means that something in the configuration structure does not port well between these firmware versions.
This is one of the reason that I don't recommend restorting configuration between different firmware versions. I'm glad you found a working solution. Congrat! :)
Yeah - I feel your pain and frustration, which is why we're all here to help or vent. Both are welcome! :-)
This is one reason why we have users factory reset and setup from scratch, then save off a new back up configuration after the new FW is in place. There are times when introducing new FW on to older FW and older cofigurations seems to break something. Even using older versions of prior FW saved configuration with new versions of FW seems to not work. Maybe due to changes in newer FW that leads to some incompatibilities with older configurations.
Going foward, if you have now saved off a new configuration to file, keep this for the current version of FW. This is one thing that has haunted NG and users over the years. When the new FW update comes around, I would make it a habit to just bit the bullet and do a reset and setup from scratch again and then save off a new backup to file for each new FW that comes out. The backups seem to work with in each FW version, migration to new FW versions doesn't.
Glad you were able to isolate the problem.
Testyblahblah wrote:
>> Repeated resets, repeated FW upgrades to the latest all achieved nothing. But, I immediately restored settings everytime...
You've just described/provided a good example for the definition of insanity, doing the exact same thing (rinse & repeate) and expect a different outcome as well as how to avoid it. Others can learn a lot from your experience.
Testyblahblah wrote:
Thanks to all in the community. No thanks to Netgear.
It was not clear in my thanks and recent replies who was being thanked. It all jumbled up and didn't make sense for you - I assumed it would quote/tag you, but didn't.Feel free to kudo the posts you like. 😊
I'm sorry you lost the time, but we all benefit a little. To reinforce what we all learned thru the school of hard knocks. Not everyone is able to spot problems so easily and problems can be subtle. I don't want to have reset my router either, but I also don't want to roll the dice and hope it works.
I'm now going to take the additional step of locking down the router.
