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.
If you have your prior router, you can use it in place of the RBR in router mode, then configure the RBR for AP mode. Disable ALL wifi radios on the prior router, then you should be stable until NG fixes this for those of you who are effected. Or downgrade to v3.1.x version on the RBR.
Thanks for letting us know. Keep in contact with NG support. Hopefully they will get this fixed soon. No idea when that will be so just keep in touch with NG support and keep an eye out here in the forums and on NG download site.
computim wrote:The CTS RTS changes from the firmware change 64 to 2347 are not solving the issue for many including myself. Good to try but make sure you read all the messages about the reboot, factory reset, CTS/RTS changes, satalite and router firmware down grading, etc.
I can confirm I've not down graded but I have done all the suggestions with no resolution to Aruba VPN tunnel failing, Wifi Calling or video conferencing frozen or dropped. My case has been escalated to engineering with the debug logs from the debug firmware installed. Along with screen shots of devices connected, advanced settings, Wan connected info, Wireless configureation infor, statistics. Awaiting the feedback.
Tim
Latest round of updates provided to NG support. One item I pointed out is the lease timeout seems to be different on the Orbi than on my R9000 X10. Lease Obtained is 30min and the R9000 if for several hours 72 to be exact. Why is the Orbi set to 30 min intervals. Seems to be about the time I notice a disconnect when a new lease is obtained. Watching more closely but maybe some others can review as well.
I have been using the X10 router for my secondary connection. 2 fiber uplinks in the house so I have a backup fiber line with the X10 and one with the ORbi Mesh.
Thanks
Tim
Something to let NG support know about.
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:
