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 ...
Do you have separated SSIDs or default single SSID? One other posted about this and there not using single SSID which seems to be one cause of the config sync issue.
A factory reset would be needed in this case and to validate the FW is working correctly. Applying over older FW may have traces of older code which should be cleared out with a reset and setup from scratch. Applying FW over older version doesn't seem to be working for NG and Orbi. Some do work and some don't. Reason for those that don't to at least try a reset and setup from scratch using default settings.
spas wrote:
Thanks Furry. Whatever success I had vanished within minutes after posting. The "config sync" cycle reappeared, devices attached to a non-existent "guest network", and multiple device are off line. I reverted back to .210 on the RBR and RBS units and everything is back to normal and working fine..
Furry, reseting back to factory defaults is not in my plan and will not be. I believe your theory is sound but shouldn't be needed for MINOR software revisions of any knid, I could see it for a major (1st digit revisions), but not for 3rd and/or 4th digit revisions.
I'll keep .210 until I find a suitable replacement.
Anyone here have any thoughts they wish to share regarding Amplifi HD, Unifi or Synology?
Are you saying that separate SSIDs are no longer supported with the 2.3.x.xx firmware releases? Is this a feature or a bug?
Separating of SSIDs has never been supported officialy by NG on Orbi.
If you have separated SSIDs, this would be the cause of the sync issue.
1midniterider wrote:
Are you saying that separate SSIDs are no longer supported with the 2.3.x.xx firmware releases? Is this a feature or a bug?- Well, the way I see it is as long as Telnet is officially supported, then making changes using the options provided should also be supported. So either remove the option or continue to support it as in prior releases. Just my two cents.
Again, it's not officially supported by NG. Telnet is included due to the fact that the Orbi FW is based on code that includes telnet support. Users can use this as they wish. However when it comes to separating SSIDs, it's NOT officialy supported. If you try the system is NG intended it to work, then you'll not see this issue of the config sync. Others are not seeing this, however they are using there systems as NG intended. Orbi does work in the intended design. If your trying to change the design, then your introducing problems and issues that you think NG is supporting. You would be incorrect in this thinking.
Good Luck.
- Probably also a matter of how much testing goes into each feature. The closer to default config, the more likely those areas have been thoroughly tested.
- We will have to agree to disagree on this issue. When a feature is deprecated, and separate SSID's is feature, no matter you slice it, it is usually listed In the release notes. So NG should officially state this feature will no longer be supported AND remove it from the config. I, like many others, have chosen to use separate SSID's because of issues that we have with some connected devices. In my household there are iPhones, Android devices, Windoze, Apple IOS and numerous other network devices, some of which were having connection drop issues, until I the Orbi to use separate SSID's. So I am not using because it is a nifty feature, but because it resolves an issue. So either NG needs to fix the connection drops or continue to support an included feature which does resolve it.
NG wont depreciate the code or feature, it's not there to depreciate. The core code and feature comes from some other sources. I believe the Orbi is based on some form of WRT code. This feature is seen in many other router code. NG and some other Mfrs don't built there own code anymore. NG wont fix something that dosn't happen using support configurations.
People been asking about separation of SSIDs for a while now, the only thing so far that NG has offered is hiding of the SSID on either radio to help those with IoT device setup problems get there devices connected.
You can surely post about it here though:
https://community.netgear.com/t5/Idea-Exchange-For-Home/idb-p/idea-exchange-for-home
Good Luck.
I'd be more interested in getting to the bottom of the disconnects instead of covering up the issue by breaking band steering .
- I have a very old Linksys that cost way less than the NG Orbi and is rock solid. Now it does have a custom WRT firmware... So my expectations is the Orbi should be just as rock solid. I am not asking NG to do anything other provide is with a rock solid solution to Home WiFi... Nothing more and nothing less. I am hoping my frustration does not get the better of so I don't turn all 5 of my Orbi devices into boat anchors.
Given the amount of effort I'm having to expend on a much simpler configuration, it would make sense for Netgear to allow Orbi customers the option of controlling firmware updates. This would be a step towards improving stability IMHO and allow the user to schedule the update and restore the network. The issue with firmware updates breaking things is not unique to Netgear, but I do know it takes time to get things working again in a satisfactory manner. I also know this issue isn't true for everyone, but my setup is very vanilla with almost all settings in default, and yet I find it necessary to factory reset after every firmware update I get. I'd just rather do it when I can rather than get stuck in an emergency having to scramble to get things back working because of something that happened overnight while I was sleeping.
Cheers
If Netgear sent quality updates that didn't require a reset this would be a moot point. Their poor quality is the core issue.
Ragar99 wrote:
If Netgear sent quality updates that didn't require a reset this would be a moot point. Their poor quality is the core issue.
If it were just Netgear having the problem I'd be more willing to indict them, but there must be something intrinsically problematic with firmware updates to routers in general that I feel compelled to factory reset . I do this reset to my Arris router as well .
I don't even trust the settings backup function and choose to reenter the settings myself.
But yeah, it would be nice if in the future these updates were transparent and non disruptive.
- I totally agree! It is well understood that factory resets and reconfiguration from scratch is often needed after a firmware update. Why would anyone think that automatically updating the firmware would be a good idea??
Thank you Netgear for creating the emergency situation with my wife and kids being very upset that our internet / WiFi is not working right.
If you want to automatically update the firmware, you have to solve the “saved configuration may not be compatible with new firmware” problem.
