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.
I would be happy to, but I actually had to pull my system down entirely and replace it with my previous Google Wifi system. I'm in the middle of planning for a product release and I won't have the time over the next couple of days to put the system back up.
What seemed to bewilder me about this is that even after reverting back to 3.2.9.1_2.4 I had the very same issues. I'm confident that I did not start seeing this issue until 3.2.11 was released, but now my system is completely toast. I'm truly scratching my head over this one, but I agree logs should help NG sort this out.
Has anyone else reverted firmware, and if so are you still seeing the issues like I am seeing?
One or two others reported downgrading and resetting and getting there systems back to stable.
Be sure that your CTS and RTS values read 2347 for both 2.4Ghz and 5Ghz under Advanced Tab/Advanced Settings/Wireless Settings
If you can't seem to get your system back to stable, please contact NG support. Open a support ticket.
xnolightx wrote:I would be happy to, but I actually had to pull my system down entirely and replace it with my previous Google Wifi system. I'm in the middle of planning for a product release and I won't have the time over the next couple of days to put the system back up.
What seemed to bewilder me about this is that even after reverting back to 3.2.9.1_2.4 I had the very same issues. I'm confident that I did not start seeing this issue until 3.2.11 was released, but now my system is completely toast. I'm truly scratching my head over this one, but I agree logs should help NG sort this out.
Has anyone else reverted firmware, and if so are you still seeing the issues like I am seeing?