NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware RBR40 2.5.1.16 keep disconnecting and auto update again after downgrade
I had a RBR40 and RBS40 which was working fine ever since I bought it last year. But since yesterday the firmware got auto upgrade to 2.5.1.16 and it had been disconnecting every few mins. I tried to...
Hi,
I have a RBK50 (RBR50 & RBS50) system and have also been going nuts the last week and a half when my satellite started acting strange with firmware update to 2.5.1.16. The wireless backhaul status kept changing from 5G to 2.4G. Stable for some time and then again disconnects and reconnects to the router and effectively the same cycle kept happening. I did all resets of both router and the satellite, but nothing worked. Then i happened to check for any updates and i found that there was one 2.5.1.32. The following were the bug fixes for the same.
Bug Fixes:
- Fixes the incorrect power setting on the WiFi Transmit Power Control
- Fixes potential issues with the Armor activation
The first bug caught my interest as i felt that it could be the reason for the switching. I updated to this firmware and did a complete reset and set it up from scratch. It been up 12hrs and everything is working stable without any switching. I think we are back to the good old days of correct good bandwidth with these mesh system.
Maybe the RBR40 might also be having the same issue and might be getting an update soon.
Hope this helps. Thanks.
-Maddy
Hello,
Since my last comments, I did nothing but changing the port that was connecting my RBR50 to the main router and somehow that did the trick, my connection been up for almost 24 hours now, with no issue. After I checked I saw that there is indeed a new FW update (2.5.1.32). However, when I checked for an update through my router setting page it is showing no new update available. Given that I have a stable connection now, do you guys think I should manually update to the new FW or do nothing since I have no issue now.
Regards,
Hitmi
IF you have no issues or problems, it best to keep whats loaded for now. You can manually download v32 FW Files and apply them if you want to. Or just download them and keep them handly for later on. v32 is a minor FW update.
AlHitmi wrote:Hello,
Since my last comments, I did nothing but changing the port that was connecting my RBR50 to the main router and somehow that did the trick, my connection been up for almost 24 hours now, with no issue. After I checked I saw that there is indeed a new FW update (2.5.1.32). However, when I checked for an update through my router setting page it is showing no new update available. Given that I have a stable connection now, do you guys think I should manually update to the new FW or do nothing since I have no issue now.
Regards,
Hitmi
madhur77 wrote:Hi,
I have a RBK50 (RBR50 & RBS50) system and have also been going nuts the last week and a half when my satellite started acting strange with firmware update to 2.5.1.16. The wireless backhaul status kept changing from 5G to 2.4G. Stable for some time and then again disconnects and reconnects to the router and effectively the same cycle kept happening. I did all resets of both router and the satellite, but nothing worked. Then i happened to check for any updates and i found that there was one 2.5.1.32. The following were the bug fixes for the same.
Bug Fixes:
- Fixes the incorrect power setting on the WiFi Transmit Power Control
- Fixes potential issues with the Armor activation
The first bug caught my interest as i felt that it could be the reason for the switching. I updated to this firmware and did a complete reset and set it up from scratch. It been up 12hrs and everything is working stable without any switching. I think we are back to the good old days of correct good bandwidth with these mesh system.
Maybe the RBR40 might also be having the same issue and might be getting an update soon.
Hope this helps. Thanks.
-Maddy
Too bad I had to replace mine since I was about to get fired for being offline all the time...
Thanks for the update!
