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.
Well these are crazy times and just happens that all of this has come at bad time.
Patience is premimum. I Get it. Trust me. However some users don't understand how coding and development work and all that goes into it. There are many levels to all this. Just can't willy nilly put something in and make it work. Doesn't work like that.
Mfrs have always been non communicative when it comes to FW updates and times frames. Some even critical. Happens accross the board. I would love to see more communications from router Mfrs. Would help belay concerns when issues arise. I get that. However on the other hand it can set a bad presidence for users and expectations that router mfrs don't want to have to deal with. So these are only a few reason why that some router mfrs don't say anything. There are legal aspects aswell.
At least when they tell you they are working on it, then let them work on it. Don't rush them and lets them them get it fixed. For now we have a working solution to get users systems back to stable. Users overly complaining and running this off the rails does nothing to help or get the problem fixed. We all know there is problem. So does NG. Its in there hands.
If you think this is the first time for any router mfr bad FW to appear on users system, think again. Not the first time and probably won't be the last. We are human. FW is based on the human condition.
computim wrote:While I can sympathize on your comment Furry I don't align with the patience piece. Many impacted users are dealing with the terrible decision NG made to push out a busted firmware. The customer base that is also being impacted by the Covid 19 situation with WAH, Self Quaratine, Kids out of school, Attempting to research or stay connected to loved one abroad. In the world of connectivity it's NG's responsibility to resolve and keep the communicty informed. This is not a time to give NG a pass on the lack of transparancy and professionalism they've exibited throughout this outage. I for one have accountability that requires a solid connection. I have contigency plans due to the nature of my business. However, for others that do not or are not as tech savy are suffering through. 10 days without a word from NG is not what I would call working on it.
Tim
FURRYe38 wrote:Well these are crazy times and just happens that all of this has come at bad time.
Patience is premimum. I Get it. Trust me. However some users don't understand how coding and development work and all that goes into it. There are many levels to all this. Just can't willy nilly put something in and make it work. Doesn't work like that.
Mfrs have always been non communicative when it comes to FW updates and times frames. Some even critical. Happens accross the board. I would love to see more communications from router Mfrs. Would help belay concerns when issues arise. I get that. However on the other hand it can set a bad presidence for users and expectations that router mfrs don't want to have to deal with. So these are only a few reason why that some router mfrs don't say anything. There are legal aspects aswell.
At least when they tell you they are working on it, then let them work on it. Don't rush them and lets them them get it fixed. For now we have a working solution to get users systems back to stable. Users overly complaining and running this off the rails does nothing to help or get the problem fixed. We all know there is problem. So does NG. Its in there hands.
If you think this is the first time for any router mfr bad FW to appear on users system, think again. Not the first time and probably won't be the last. We are human. FW is based on the human condition.
Hopefully you're not counting me in the "some users don't understand how coding and development work" because I can assure you I do. This is my profession and my livelyhood depends on connectivity, now especially.
Oh, and I have yet to see NG publicly mention that they are working on it. So yeah, I am out of patience with NG.
Sorry for the rant, but your $700 router is working, so no you dont get it.