NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bjosh
May 17, 2022Follower
Is there ETA for the fix also is NG going to push the fix
Is there ETA for the fix also is NG going to push the fix since we are unable to login to the router through the browser or app.
FURRYe38
May 17, 2022Guru - Experienced User
I don't think it's the Fw that's the problem, more like how its being deployed thru auto updates. I and others have had v.2 loaded since before NG started pushing the same version via AU. Ours was loaded manually. Have not seen any problems accessing the RBRs web page. Also maybe some problems in auto updating systems from older versions of v4 to new v.4 versions as well. I believe mostly this is a AU issue that hasn't been fully addressed or tested fully by NG in how AU works.
claudiut
May 17, 2022Apprentice
I can confirm that loading the firmware (v4.6.8.2) manually works (so far) without issues. I'm able to access the router and satellites through web interface and Orbi app.
To be completely honest I'm not 100% convinced it's not a FW issue as FURRYe38 implies, but in the end, it doesn't even matter. NG should get their s^#% together and fix this mess that goes on for way too long.
- FURRYe38May 17, 2022Guru - Experienced User
Historically AU has seen many issues over time, even on Orbi AC models. Not the first time AU has broke users systems.
NG will hopefully take heed this time. I agree, they messed up big time. Hoping they will do something.
Keep your v.2 FW files on hand.
- FURRYe38May 17, 2022Guru - Experienced User
It only a small part. AU system we believe it's it own beast that out of control.
Never mentioned putting fault at users configurations. This event is certainly on NG. I only explained that some of us who had v.2 already loaded prior to NGs AU event weekend before last didn't' see problems. This doesn't mean this is a user configuration issue or was directed at users configurations.
- FURRYe38May 17, 2022Guru - Experienced User
OF course...that's also in case where we have to troubleshoot the issue to really find out where the problem is, FW or user configuration. Its not always a FW issue and sometimes it is. Just be cause one user claims its a FW issue doesn't mean it is. The real problem has to be vetted out. I can point to many posts that were resolved as well by troubleshooting or factory resets.
Over all, this is a NG issue and items for resolution have been presented and work. NG has acknowledged the issue and is working to get it fixed. Users will need to contact NG support if they want there help. Or factory reset and setup from scratch. This is mostly beyond forum help now.