NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi Firmware update 2.5.0.38 problems
Have a 2 year old RBR50 with 2 satellites - have had no problems until recent update to 2.5.0.38. Everything is working howerever the GUI now has issues when attempting to display devices. The web ...
The reset and setup from scratch on the RBR will probably fix the issues your seeing. Try then when your ready.
RonRolfsen wrote:After several reboots still have the problems (no Main page, no devices attached). I wanted to downgrade to 2.5.0.30 but now when I go to the Advanced-Administration-Firmware Update in the web gui get the:
400 Bad Request
This server does not support the operation requested by your client.
Mobile app does not allow a firmware downgrade as far as I can tell.
Is there a way to telnet into the router and downgrade the firmware?
(have not yet tried reset - saving as last resort since things are 'working')
A factory reset is a last resort method to check for problems and resolution. Though I and a few others use this in our normal manual FW updates methods, I understand that users shouldn't have too. However, again when problems appear or appear after FW updates, and all other troubleshooting has been exhausted, then a reset and setup from scratch should be performed. Seen many problems resolved after a reset. Lingering prior FW code or user mis-configurations with newer versions of FW code seem to cause problems. Resets allow the FW to be cleared out and start fresh.
To save time on factory resets and configurations, you should already be using Backup Configuration files. These save time. Do you not know about this feature?
v38 is working for me and others. You don't have to use it as well. Use what works for you.
PetervdK65 wrote:I don't know your setup, but the advice to do a factory reset after every FW update is very weird. A factory reset will cost me a day to get every thing setup as before. During that time, all my camera's and other security devices won't be operational. That should not be necessary with an expensive system like this. In fact, if i really had to factory reset every time an update was issued, i would certainly dump the whole system.
FURRYe38 wrote:A factory reset is a last resort method to check for problems and resolution. Though I and a few others use this in our normal manual FW updates methods, I understand that users shouldn't have too. However, again when problems appear or appear after FW updates, and all other troubleshooting has been exhausted, then a reset and setup from scratch should be performed. Seen many problems resolved after a reset. Lingering prior FW code or user mis-configurations with newer versions of FW code seem to cause problems. Resets allow the FW to be cleared out and start fresh.
To save time on factory resets and configurations, you should already be using Backup Configuration files. These save time. Do you not know about this feature?
v38 is working for me and others. You don't have to use it as well. Use what works for you.
PetervdK65 wrote:I don't know your setup, but the advice to do a factory reset after every FW update is very weird. A factory reset will cost me a day to get every thing setup as before. During that time, all my camera's and other security devices won't be operational. That should not be necessary with an expensive system like this. In fact, if i really had to factory reset every time an update was issued, i would certainly dump the whole system.
Just to clarify, a backup config file should NOT be applied to a new rev of firmware. If one is compelled to update, the setup should be done via the new firmware GUI. Using a backup config file may reintroduce the same issues as if you had only done an in place update. BUT, it is nice to have if you downgrade to the pervios rev you were running after a problematic update with factory reset.