NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - NetGear Orbi Firmware Version 2.3.0.32 now available...
FW 2.3.0.32 is now available on our support site :
https://www.netgear.com/support/product/RBK50.aspx#download
RBR/RBS 50 Series Only.
To manually update the firmware, there is a need to ...
Has anyone else had issues with Armour enabled? I upgraded the the firmware yesterday but started getting problems with browsers on multiple devices reporting insecure connections and invalid certificates last night along with Echos being unable to connect. Disabling Armour appears to have fixed it so far.
porlockweir Its interesting that you are seeing these issue when Netgear Armor is enabled. I have been running Armor on my Orbi for past month or so on both beta and official 2.3.0.X FWs and have not observed these issues. If its not too much hassle can you back up your configuration and reset Orbi to factory settings and see if issue occurs? If the problem does not occur in default factory settings with Armor enabled load the backup config file and see if issue can be reproduced. If you can consistently reproduce the issue I would recommend to reach out to Netgear to have them investigate.
Thanks for the advice - I'd had to do this with my prevuous Nighthawk but it's a real pain having to set eveyting up from scratch as the backup never seems to include every setting. I finally got it to work last weekend after 3 factory defaults, including one due to it randomly deciding to block allowed devices on access control. Perhaps Netgear needs to look at other technology manufacturers to see how a firmware update should work, as my experience with this one was very poor with hours wasted due to the bugs they didn’t spot. I now have had Armor running for a week and it seems pretty good especially with he unlimited device subscription to Bitdefender – only issue so far is that it has declared my ReadyNAS that has just been updated to the latest firmware (a much better experience than the Orbi!) as being insecure even though it should be locked down - but irritatingly just displays a blank box when I click on it to find out what this issue is.
Yes factory resets seem to be needed after doing autoupdates. I know it's a pain to setup.
However I recommend after doing a factory reset and set up from scratch, do a new BACKUP configuration to file so that you have a new back up file to use with the new FW update. In some cases, the older backup configs may or may not work so to avoid any issues, it's best to save off a new after a FW update and configuration has been completed.
porlockweir wrote:
Thanks for the advice - I'd had to do this with my prevuous Nighthawk but it's a real pain having to set eveyting up from scratch as the backup never seems to include every setting. I finally got it to work last weekend after 3 factory defaults, including one due to it randomly deciding to block allowed devices on access control. Perhaps Netgear needs to look at other technology manufacturers to see how a firmware update should work, as my experience with this one was very poor with hours wasted due to the bugs they didn’t spot. I now have had Armor running for a week and it seems pretty good especially with he unlimited device subscription to Bitdefender – only issue so far is that it has declared my ReadyNAS that has just been updated to the latest firmware (a much better experience than the Orbi!) as being insecure even though it should be locked down - but irritatingly just displays a blank box when I click on it to find out what this issue is.
Updated from 2.2.1.210 to 2.3.0.32 and now have issues. I purchased the RBK53 Costco pack (1-RBR50/2-RBS50s) a couple years back and have NOT have any issues with ANY firmware versions till now. I separated the 2.4 and 5ghz SSIDs as per instructions from another thread since the beginning.
I went through the manual firmware upgrade procedure from V1.210 and installed V0.32 (thru 2.2.1.212) without issue (satellites first, then base unit). The RBR50 is in Router Mode.
1: Traffic Meter no longer is complying statistics.
2: The IOS App incorrectly shows the network map. I’m configured as a STAR, but the app bounces between STAR and Daisy-Chain topology.
3: The WEB GUI | ATTACHED DEVICES | CONNECTED SATELLITES | Bounces between “GOOD” and “Conifg Sync” status all the time.
4: Internet connectivity drops multiple times a day. Never happened with previous firmware versions.
5: After rebooting the Orbis. It usually 2-3 days for all the IP devices (24) to “settle –in” as I call it, where wireless devices attach to either Router or Satellite based on distance/proximity. This has been disrupted with V0.32. It was stable before but no longer. Some IP devices jump from one Orbi to another like never before.Anyone else experiencing anything similar?
