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.
NG is working on it. Any new FW maybe delayed due to the CD19 mania thats running around so don't be surprised by how much longer this may last. Lots of people working from home now. Users need to be patient please.
Users can downgrade to v3.1 while you wait for NG next update if your having problems:
FURRYe38 wrote:NG is working on it. Any new FW maybe delayed due to the CD19 mania thats running around so don't be surprised by how much longer this may last. Lots of people working from home now. Users need to be patient please.
Users can downgrade to v3.1 while you wait for NG next update if your having problems:
This is no excuse for NG not providing any communication around this issue. Sorry, but you need to stop defending them. If you were in our shoes, your tune would be different.
I'm not defending them. Trying to help users get there systems back up and running in mean time. There is a working solution. Use it.
Router mfrs don't communicate anything when it comes to FW and there development and release. Good Luck in getting that from any router mfr. Just because I and others are NOT having problems doesn't mean we don't care either.
If your so upset, make contact with NG support or return the system and find something else. Nothing else anyone here in the forums can do. This has to be handled by NG.
In mean time, users will have to wait. We all do hope a fix comes soon.
Good Luck.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
FURRYe38 wrote:I'm not defending them. Trying to help users get there systems back up and running in mean time. There is a working solution. Use it.
Router mfrs don't communicate anything when it comes to FW and there development and release. Good Luck in getting that from any router mfr. Just because I and others are NOT having problems doesn't mean we don't care either.
If your so upset, make contact with NG support or return the system and find something else. Nothing else anyone here in the forums can do. This has to be handled by NG.
In mean time, users will have to wait. We all do hope a fix comes soon.
Good Luck.All I am saying is that a lack of communication around a botched firmware that is causing major issues for many people at the worst possible time is simply unacceptable. Providing simple status updates to us is all we're asking.
Oh, and I have already contacted NG support, contacted the guy on this forum that did nothing and provided no information, and have installed the 3.1 firmware (and even managed to block the auto upgrades). I did all of this despite the lack of communication from NG. It sure would have been nice to have NG actually give us a working solution instead.
In the meantime, enjoy your working router and please understand where the rest of us unlucky ones are coming from.
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
Most of us are working from home *because* of covid-19. They should be working double shift to fix the issues for their customers who are stranded at home. Their development teams have been subcontracted to China and/or India long ago, those countries, especially China, have been dealing with covid-19 for months, that didn't prevent them from releasing a new (and botched) firmware last week.
Sorry for the rant, but victim card denied.
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.
cruisencode I totally understand. Trust me, I get and and understand everyones concern and feelings. I have had my feelings up and down since I got Orbi as well. How would you feel if you couldn't use the Orbi AX in router mode since you first bought it as it caused BAD NAT status on your game consoles. I've been dealing with this since day ONE and could only use it in AP mode up until v10.11 arrived. I'm with you on how it feels man.
Been working in forums for quite a while know so i've seen many things, including repeated bad FW releases. I do wish there was more communication. I've been asking as well on everyones behalf. Even submitted a bug report first day as well. I also don't want to push too much as, again, NG is aware of this and during this crap time frame with the CD19 mania running around and it's impacting business as usual, I dont' wanna push where pushing isn't needed or desired. Pushing too much right now isn't going to yield anything. There are some legalities that probably prevents NG from communicating as well. They know about. Lets let them figure this out. I'm here to help users as best as I can to get back to stable. Thanking other users for there help in this is important as well.
All we can do is be patient and try the work around solutions to get your systems back to stable for now. For those that have the ability to return there systems, this you'll need to consider.
cruisencode wrote:
FURRYe38 wrote:I'm not defending them. Trying to help users get there systems back up and running in mean time. There is a working solution. Use it.
Router mfrs don't communicate anything when it comes to FW and there development and release. Good Luck in getting that from any router mfr. Just because I and others are NOT having problems doesn't mean we don't care either.
If your so upset, make contact with NG support or return the system and find something else. Nothing else anyone here in the forums can do. This has to be handled by NG.
In mean time, users will have to wait. We all do hope a fix comes soon.
Good Luck.All I am saying is that a lack of communication around a botched firmware that is causing major issues for many people at the worst possible time is simply unacceptable. Providing simple status updates to us is all we're asking.
Oh, and I have already contacted NG support, contacted the guy on this forum that did nothing and provided no information, and have installed the 3.1 firmware (and even managed to block the auto upgrades). I did all of this despite the lack of communication from NG. It sure would have been nice to have NG actually give us a working solution instead.
In the meantime, enjoy your working router and please understand where the rest of us unlucky ones are coming from.
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.
