V2.1.1.12 is not ready for public release

I can't easily return this thing because it's across a border and some distance, so I guess my only option is to keep banging on the drum here now that I am past my 90 day support window - which is entirely too short for such an expensive product. I've had better support for childrens toys.

Anyways. My devices now all show as connected through the router - none show up on satellites. Day 2 on this issue with no acknowledgement from Netgear which is really frustrating. Don't go to this firmware.

I guess I am one of the lucky ones then. My Orbi 50 has become more stable since the latest FW upgrade. I do continue to miss WiFi Scheduling and this needs to be brought back (as per user manual) as this is a potential showstopper for me.

Netgear employees could be a bit more present in this forum though. Comparing it with the ReadyNAS forum, there is a high involvement of Netgear employees, who even offer to send them - if necessary - your logfiles to help them with resolving your problems.

The ReadyNAS experience makes me stick with Netgear (for now) and I just keep hoping that the same experience will be the case for the Orbi community here.

Netgear Orbi folks! If you are reading this, please talk to your Netgear ReadyNAS colleagues and learn from them!

I'm having the same issue.   My router/satellite will disconnect every couple hours.  All my devices are connected to the router (only).

My devices will go offline from time to time, getting choppy videos and voice calls.

Is there a way you can share the v2.0.1.2 firmware?

The same experience that I had with my RBK53.  All was perfect - in fact, excellent - until I updated to the 1.12.0.18 firmware.  Went from excellent to unusable.  I tried everything, including resets, NVRAM reset, trying to revert to previous firnware, etc.  Finally, I was exasperated enough to call it quits.  I got an Eero and have been pleased as punch ever since the day that I fired it up.  As an experiment, I updated the Orbi to 2.0.0.74 using it as an access point, and that version seems to be stable (obviously, I didn't take the time to check everything out, since the Eero system is so stablew.  So, I'm "gifting" it to friend to try out with the 2.0.0.74 firmware- Hopefully, it will work for him with V2.0.0.74 and not push to 2.1.1.12.  I don't like the idea of transferring my old problems to a friend, so I hope that it works well.  I'm not about to ask for any money in return for a questionable product.

---

ThePathfinder wrote:

For those of you that have a stable working Orbi with V2.1.1.12 I say congratulations, last January I purchased my RBK53 Orbi from Costco and it has been a long winding road. I have always been a Netgear customer never owned anything but. Out of the box the Orbi provided a much better solution than my WNDR4500 but then came the first of many firmware updates that would bring with them nothing but problems albeit mostly minor to medium issues such as random disconnects. But with the help of DarrenM I was put in contact with tier 2 support and after a few different beta versions I finally landed on V2.0.1.2 which made the Orbi what it should be, a set it and forget it device. I was content to never upgrade the firmware again and just enjoy the working product for which I paid a considerable amount of money, but then came the KRACK vulnerability so when V2.1.1.12 was offered I figured it had to be built on the beta code that had proven itself so stable for me. But as I document above that is not the case, so I moved back to the known good firmware thinking I would wait for Netgear to acknowledge the issue and provide a fix. But while I see DarrenM acknowledging some of the issues I see nothing from Netgear in the way of a suggestion or a fix. But back to the issue at hand so having moved back to the previous firmware I was surprised to find I was now having random and frequent satellite disconnects I defaulted everything and reprogrammed but still the issues persisted. All I can assume is the newest firmware made changes to the hardware that are not reversed by moving back to an older firmware. So today I again defaulted everything and again loaded V2.1.1.12 and it went from bad to simply unusable I cannot use the OOMA to make calls as it cuts in and out (never an issue before) and the satellites drop offline even more frequently. Along with now the main router drops offline randomly as well.  I let it run all afternoon and evening hoping it might somehow stabilize but NO. So I again moved it back to the beta so I could at least have stable hardwired connections. I did send a PM to DarrenM earlier today and had hoped he might contact me with some options but as my wife pointed out I have spent enough time on this thing its time to move on. Luckily, I had purchased it from Costco and when I contacted them they said no problem bring it in for return. SO I guess today is the day that the Orbi put an end to me being a Netgear customer. The eero Pro WiFi System has been ordered and will be here on Monday. By the way I reached out to eero today with some questions and they were immediately accessible.  They also made it clear that if I had any problems now or down the road they were available to help. None of this 90-day support BS. Its sad I really feel Netgear has forgotten how important it is to take care of the customer. To everyone on this forum that offered help and advice to me THANK YOU. To Netgear I say get your house in order you just lost what had been and would have been a lifelong customer.

---

Your experience with the Orbi is much the same as was mine; however, I got off the Orbi trainwreck about three months ago when I sidelined it and purchased the Eero Pro.  Knock on wood, but the Eero has been freakishly awsome. Not a single problem, and absolutely no regrets - period.