NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi Firmware v3.2.10.11 seen on your RBRs FW update check page?
Just curious if anyone out here in the public forum are seeing this version pop up as available on there RBRs web page? IF so, please post what version of FW you currently have loaded. Up to y...
Problems seen on v10.11 since 3/9 have been addresses and fixed by NG. They reported that it was something having to do with there cloud systems. v10.11 FW was put back up on there auto update servers for users to download as of 3/19. These problems have been resolved.
If users are noticing any futher problems please make a new post about it or contact NG support.
Enjoy.
Try using IP reservation for all your devices on your RBK850 and see if that solves the disconnects. I have all my devices set this way and have had no problems with this firmware.
Everything was working fine before Firmware v3.2.10.11.
Why just go back to previous version instead of all this multiple problems? What is NG trying to accomplish with this new firmware?
Some users have gone back to prior version and are still having problems. Not sure if the auto update services are the main cause or application of FW over current configurations are another cause. Some of us got this a couple of weeks ago and have not seen any problems aside the CTS/RTS values being changed. Even then, systems have been working. We considered this most stable to date. Even allowed me to use mine in router mode since before this version, I could not due to gaming problems in prior FW versions. So maybe based on this NG said lets give it a push to the public. I really think NG auto push update services are the main cause. Why? who knows.
Have you downgraded?
DoctorA wrote:Everything was working fine before Firmware v3.2.10.11.
Why just go back to previous version instead of all this multiple problems? What is NG trying to accomplish with this new firmware?
Well said FURRYe38. Another thought on the firmware is that downgrading doesn't necessarily address the area that was changed in the latest firmware. Lets make up a couple fields AB&C in firmware X were addressed and all were working good. In firmware update Y only fields A&B were updated and in firmware Z fields E&F were updated. I've over simplified this for an illustration but the idea is reverting back to older firmware may not address the field update that is causing the issue. That is why NG needs to address the update wholistically in order to revert of remediate the fileds that where changed.
Tim
Well said too. We can only hope NG will get this addressed soon.
Just be patient. :smileywink:
