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...
In addition to turning off the auto-update setting, I suggest replacing that text file.
Since you now have V2.3.5.30 on both router and satellite, log into each with telnet and type:
echo V8.3.5.30 > firmware_version
cat firmware_version
The "8" is nothing special as long as it is greater than any possible Orbi firmware. Netgear is still on V2.3.7.33, so it seems unlikely they will get all the way to V8(something) any time soon.
Both of these hacks (auto update and version number) last only until the next time the router reboots. The reboot causes firmware to be reloaded from read-only memory and the changes will disappear. Soon after that, the Orbi will discover new firmware and update on its own.
I have my both my Orbi router and satellite on UPS so that power has to be out for a minimum of 30 minutes before they shut down and wake up when the electricity is restored. This happens maybe 1-2 times a year.
CrimpOn wrote:In addition to turning off the auto-update setting, I suggest replacing that text file.
Since you now have V2.3.5.30 on both router and satellite, log into each with telnet and type:
echo V8.3.5.30 > firmware_version
cat firmware_version
The "8" is nothing special as long as it is greater than any possible Orbi firmware. Netgear is still on V2.3.7.33, so it seems unlikely they will get all the way to V8(something) any time soon.
Both of these hacks (auto update and version number) last only until the next time the router reboots. The reboot causes firmware to be reloaded from read-only memory and the changes will disappear. Soon after that, the Orbi will discover new firmware and update on its own.
I have my both my Orbi router and satellite on UPS so that power has to be out for a minimum of 30 minutes before they shut down and wake up when the electricity is restored. This happens maybe 1-2 times a year.
RBR50: Done
RBS50: Have not logged on with telnet and made any setting changes. Hope I only needed to do it on RBR50 and not the satellite. Tried to log on, but the username and pw I use to log directly on to it won't be accepted in telnet. Not sure why (have also enabled Telnet on RBS50)
MartonDotNO wrote:
RBS50: Have not logged on with telnet and made any setting changes. Hope I only needed to do it on RBR50 and not the satellite. Tried to log on, but the username and pw I use to log directly on to it won't be accepted in telnet. Not sure why (have also enabled Telnet on RBS50)Very strange. I just logged into my RBS50 satellite using the same credentials that I use for web login and for telnet to the router. ("admin" and the password)
Maybe there was a typo when entering the password?
- Ye it is strange. Not a typo. Even tryed with another keyboard
MartonDotNO wrote:
CrimpOn wrote:In addition to turning off the auto-update setting, I suggest replacing that text file.
Since you now have V2.3.5.30 on both router and satellite, log into each with telnet and type:
echo V8.3.5.30 > firmware_version
cat firmware_version
The "8" is nothing special as long as it is greater than any possible Orbi firmware. Netgear is still on V2.3.7.33, so it seems unlikely they will get all the way to V8(something) any time soon.
Both of these hacks (auto update and version number) last only until the next time the router reboots. The reboot causes firmware to be reloaded from read-only memory and the changes will disappear. Soon after that, the Orbi will discover new firmware and update on its own.
I have my both my Orbi router and satellite on UPS so that power has to be out for a minimum of 30 minutes before they shut down and wake up when the electricity is restored. This happens maybe 1-2 times a year.
RBR50: Done
RBS50: Have not logged on with telnet and made any setting changes. Hope I only needed to do it on RBR50 and not the satellite. Tried to log on, but the username and pw I use to log directly on to it won't be accepted in telnet. Not sure why (have also enabled Telnet on RBS50)Update: 21.09.21 - 11:01
RBR 50 - Router Firmware Version, V8.3.5.30 cat firmware_version (is this a good sign?!?!)
RBS50: Firmware Version: V2.7.3.22 now. So looks like the **bleep** has updated it self sometime when I was sleeping.
Tryed to log on to the IP address to my RBS50 right now and it wont let me even connect today. Yesterday I was able to get as far as du put in username and password, but even with the correct one I was not able.
Today it says: can not open a connection to host, on port 23: can not connect (see added screenshot)Screenshot RBR50 status
Screenshot RBS50
Certainly looks as if the satellite auto-updated. It is a real struggle to keep this from happening. I am not confident that the "auto update" setting does anything. I am very confident that the firmware_version trick does because that is what Voxel does to keep his firmware from getting updated by Netgear. Voxel has made substantial changes to Orbi firmware, but there are many parts of the code that are binary to begin with and he cannot change or recompile them. Whatever code handles updating is in the part that he cannot change. Once he began changing firmware_version, his firmware is no longer affected by Netgear's update routines.
CrimpOn wrote:Certainly looks as if the satellite auto-updated. It is a real struggle to keep this from happening. I am not confident that the "auto update" setting does anything. I am very confident that the firmware_version trick does because that is what Voxel does to keep his firmware from getting updated by Netgear. Voxel has made substantial changes to Orbi firmware, but there are many parts of the code that are binary to begin with and he cannot change or recompile them. Whatever code handles updating is in the part that he cannot change. Once he began changing firmware_version, his firmware is no longer affected by Netgear's update routines.
Ok. Not i have been able to access both on telnet and added the "cheat" version code you gave me. So now both have the same.
Crossing my fingers again to see if it sticks. But it looks ok and thanks again so much for everything.
Not even sure what post I need to mark as solution.Funny thing.. for some reason the password on the login telnet on the satellite was nothing. Tryed just to hit enter and I got in. Scary also
One can try Voxels FW on your Orbi system:
https://community.netgear.com/t5/Orbi/Voxels-FW-available-for-50-series-Orbi-only-available/m-p/1883615#
https://www.snbforums.com/threads/custom-firmware-build-for-orbi-a-la-faq.65224/
You can revert back to stock FW if it doesn't work out for you.
