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.
This is the only work around currently that others are posting that is helping there systems get back to stable state:
computim wrote:Furry - You say there is a working fix? I've attempted all as have many others and the fix does not fully resolve. The issue still persists as indicated in my logs to engineering. They have confirmed that that last firmware pushed caused an issue that downgrading will not address. Just becasue you are not experiencing doesn't mean other are having a good experience. Everyone appreicates the attempts to resolve and the shared information. However, if the fix was so simple why hasn't NG pushed a new firmware. This is not about you this is about a community of impacted customers. NG really needs to provide the resolution here.
Tim
I can confirm that the blocking the upgrade path only prevents the upgrade.. However, the lower firmwares do not address the issue that was created due to the last firmware update that created the issue. This has been confirmed with the NG engineering team and that is why they have not recommended as a fix.
Its not a fix, its a work around. It's helping those to get there systems back to more stable state.
computim wrote:I can confirm that the blocking the upgrade path only prevents the upgrade.. However, the lower firmwares do not address the issue that was created due to the last firmware update that created the issue. This has been confirmed with the NG engineering team and that is why they have not recommended as a fix.