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 ...
Hello All,
Since upgrading from v2.2.1.210 (via v2.2.1.212), my satellites ( one RBS50 and two RBW30) frequently perform a "config sync". I've performed a factory reset on all devices and it continues to "config sync". Any other ideas?
- Assuming you did upgrade to 2.3.02 after 2.12 pit stop?
- Sorry meant 2.30.32 but for your rbw30 it looks like 2.3.04
https://kb.netgear.com/000060601/RBW30-Firmware-Version-2-3-0-4Yes, all are on the latest firmware.
Is Daisy chain enabled? Try disabling it.
1midniterider wrote:
Hello All,
Since upgrading from v2.2.1.210 (via v2.2.1.212), my satellites ( one RBS50 and two RBW30) frequently perform a "config sync". I've performed a factory reset on all devices and it continues to "config sync". Any other ideas?
Thanks to all responders...I reverted back to .210 on the router and both satelittes this morning... So far, so good - All issues --> gone...
- traffic meter working again,
- IOS app (2.3.0.31) correcly displaying (STAR) topology,
- Web GUI - no more satellite "config sync" bounces, satelittes show "good" all the time
- no internet drops.
- devices already connecting to closest Orbi
I guess I'll wait till the next firmware release before thinking about upgrading...
Cheers!
Did you factory reset and setup from scratch after updating to v32?
Was Daisy chain enabled? Disable it if it was.
Others are not reporting these issues after a reset. Next time please give feedback to questions presented to you. Helpful to know more of what you did.
spas wrote:
Thanks to all responders...I reverted back to .210 on the router and both satelittes this morning... So far, so good - All issues --> gone...
- traffic meter working again,
- IOS app (2.3.0.31) correcly displaying (STAR) topology,
- Web GUI - no more satellite "config sync" bounces, satelittes show "good" all the time
- no internet drops.
- devices already connecting to closest Orbi
I guess I'll wait till the next firmware release before thinking about upgrading...
Cheers!
I had disabled it and was still getting the config sync issue. I see where one user reverted back to .210 to correct the issue. Maybe I'll give that a try.
Please try a factory reset on the base and satellite(s) first before reverting back. Would like to see if this might clear this up.
Please set a IP address reservation for the satllite(s) ON the base after you get the satellite(s) connected.
If not, then we can have NG support review this.
1midniterider wrote:
I had disabled it and was still getting the config sync issue. I see where one user reverted back to .210 to correct the issue. Maybe I'll give that a try.
>> Since upgrading from v2.2.1.210 (via v2.2.1.212), my satellites ( one RBS50 and two RBW30) frequently perform a "config sync". I've performed a factory reset on all devices and it continues to "config sync". Any other ideas?
You are not alone with this problem. I ran into the exact same issue post upgrade from v210 to v32. Don't waste time with Factory Reset or any configurations fiddling, it won't resolve the 'config_sync' vicious cycles problem. The Satellites will have connection problem when this happens. You can verify this by going to RBR50 Firmware Update page. The Satellites would say "Waiting for connection" instead of "No new firmware version available". The latest Orbi app will also go crazy trying to determine the network map topology. The network map will change constantly on every other refresh.
The solution that works for me was to revert back to v210. I'm sticking with v210 until the next firmware release.
- I reverted back to .210 yesterday and everything is back to normal except traffic meter. I’m with you on waiting to the next firmware upgrade.
I downgraded the RBR50 to .210, which appears to have stabilized for the moment.
I went back to 210 also. Router and Satellites. I was seeing random speed drops and just didn't have the desire to troubleshoot more Netgear bugs.
