NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi RBR50/RBS50 - Cannot downgrade firmware
My RBR 50 (router) and my RBS 50 (Sattelite) won't downgrade! RBR 50: V2.7.3.22 - current version RBS 50: V2.7.3.22 - current version ISSUE nr 1: Multiple times a day my RBS 50 losses con...
There have been many reports of customers using the Manual Update tab on the Firmware Update page to load previous firmware on the Orbi. During this process, the Orbi will reboot, which causes the web browser to lose the connection. When the router has finished rebooting, the web page has to reauthenticate and get connected again. The steps are normal. What is not normal is the firmware not changing.
Those reports also describe their Orbi systems automatically updating to version 2.7.3.22 again. This puts them back with the problem which caused them to load previous firmware. A vicious circle. There are ways to prevent the autoupdate, either:
- Adding an inexpensive router upstream of the Orbi and having that router block access to the Netgear firmware update sites, or
- Using telnet to change the version number stored in memory so that it does not recognize the new version as 'newer'. This hack has to be reapplied any time the router reboots (a nuisance).
It is an ugly situation for some customers. And clearly worse in your situation if the manual update process does not work at all.
Hi, didnt know anyone replayed to my post. So thanks and sorry for the late respons.
Ok, so reboot =loose conmnection, makes sense of course.
So going forward. do you know the url i need to block for not the router to download the update manualy?
Telnet sounds like an option that will be to advanced for me.
Can also add that when this connection breaks with my sattelite i an not even get on the WEB UI on it. So if im wired to the sattlite i can access it with 192.168.1.3, but when this connection issues hits me im not able to do it.
Has a factory reset and setup from scratch been performed since last FW update?
Yes, reset has been preformed and sad to say it didnt resolve it.
Hi again, took the time to look at a video on Telnet enable feature on the Router don't look to be an option here for me. Might have been removed on the newer firmware?
There appear to be several issues being discussed at the same time:
- A connection issue between router and satellite
I get the sense that this issue was not present before the router updated to V2.7.3.22.
Is this correct?
If so, then manually loading previous firmware might be a temporary solution until Netgear produces new firmware which corrects the problem. - Unable to manually load previous firmware on the router and satellite
- Preventing the router/satellite from automatically updating firmware to V2.7.3.22
Manually loading firmware is best done when connected directly to the router or satellite. i.e. after downloading and unpacking the *.img files for both router and satellite:
- Connect directly to the router (192.168.1.1), navigate to the Firmware Update, Manual Update tab, select the firmware and update.
- Connect directly to the satellite (192.168.1.3) and select Firmware Update from the home screen menu.
Every time I have done this, the manual upload has worked and when the device restarts it has the version that was uploaded. What has been reported in the forum is that the router sometimes notices the available firmware and does an automatic update again. There may be a very small window to prevent this. It will certainly prevent auto-update if the router is temporarily disconnected from the Internet.
There are two options for preventing auto-update:
- Place a router between the Orbi and Internet which blocks access to http.fw.updates1.netgear.com
This can be any old router. Could even be the ISP combination modem/router.
This does create a "Double NAT" condition which interferes with certain applications.
https://kb.netgear.com/30186/What-is-Double-NAT
But it's a choice (a) have no Double NAT and experience problems, or (b) fix the primary problem and live with the consequences of Double NAT.
When access to http.fw.updates1.netgear.com is blocked, the Orbi cannot auto-update. - User telnet to block the Orbi from recognizing that newer firmware is available by replacing the file firmware_version with a bigger number than any possible Orbi firmware from Netgear.
Netgear removed the telnet option from the debug page starting with V2.7.3.22, so if a previous firmware has been installed on the router & satellite, the telnet option should be there.
Thanks for the follow
CrimpOn wrote:There appear to be several issues being discussed at the same time:
- A connection issue between router and satellite
I get the sense that this issue was not present before the router updated to V2.7.3.22.
Is this correct?
If so, then manually loading previous firmware might be a temporary solution until Netgear produces new firmware which corrects the problem. - Unable to manually load previous firmware on the router and satellite
- Preventing the router/satellite from automatically updating firmware to V2.7.3.22
Manually loading firmware is best done when connected directly to the router or satellite. i.e. after downloading and unpacking the *.img files for both router and satellite:
- Connect directly to the router (192.168.1.1), navigate to the Firmware Update, Manual Update tab, select the firmware and update.
- Connect directly to the satellite (192.168.1.3) and select Firmware Update from the home screen menu.
Every time I have done this, the manual upload has worked and when the device restarts it has the version that was uploaded. What has been reported in the forum is that the router sometimes notices the available firmware and does an automatic update again. There may be a very small window to prevent this. It will certainly prevent auto-update if the router is temporarily disconnected from the Internet.
There are two options for preventing auto-update:
- Place a router between the Orbi and Internet which blocks access to http.fw.updates1.netgear.com
This can be any old router. Could even be the ISP combination modem/router.
This does create a "Double NAT" condition which interferes with certain applications.
https://kb.netgear.com/30186/What-is-Double-NAT
But it's a choice (a) have no Double NAT and experience problems, or (b) fix the primary problem and live with the consequences of Double NAT.
When access to http.fw.updates1.netgear.com is blocked, the Orbi cannot auto-update. - User telnet to block the Orbi from recognizing that newer firmware is available by replacing the file firmware_version with a bigger number than any possible Orbi firmware from Netgear.
Netgear removed the telnet option from the debug page starting with V2.7.3.22, so if a previous firmware has been installed on the router & satellite, the telnet option should be there.
Thanks for the follow-up. Got a similar idea based on your solution that helped me tonight. And I think it's solved.. I hope!
Your input was: downgrade the individual units. Tried that before, since I don't have an old router to set up for a block I did the next best thing and joinked the internet connection with the firmware v2.3.5.30 pre downloaded and ready to be uploaded to the RBR 50 and RBS50 that was stable for me before this update.
When the v2.3.5.30 was installed i turned on the Enable Telnet feature in the 192.168.1.1/debug.htm and turned off the auto upgrade settings in the CMD(telnet).
Fingers crossed that this runs stable now and thanks a lot for all the help and input.
Next issue to solve is to get my Miele Dryer to connect to the Wifi :) Have a good night- A connection issue between router and satellite
- A connection issue between router and satellite
