NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi firmware update v2.1.4.16 availability
We’ve been monitoring issues that some customers have experienced in OrbiOS 2.1.4. In response, we’re releasing firmware that provides a permanent fix for the homekit issue along with various other f...
Lets try to help him first and see if there is a problem else where or with FW. Doesn't hurt to try a few things first while we all wait for the next FW update even though others are having good experiences with current FW versions. Not everyone is having bad experiences. Takes some effort to troubleshoot what the real issue is. It's not always FW.
A system that requires specific actions, disabling of features/functions, or specific hardware to allow it to work is not "troubleshooting" ... it's a flaw that cannot be fixed by bandaid approaches.
And you can certainly believe that.
Meanwhile I'll continue to try and help others and help find the real issues.
- It doesn’t. Mine has been up and operational since December without a single issue they two automatic firmware updates
Like tsig, my orbis just work, so a fully functioning, stable Orbi network is achievable
I was able to see my sattalite listed as a sattalite in the list on the Main unit before 2.1.4.16 the release prior. Nothing has changed in my setup since then. Orbi RBR50 is in AP mode and I have one satellite wired backhaul. I have a gigabit down/up googlefiber and all my cabling is new cat6 and cat7 high quality. I have a switch s8000 Netgear in the mix.
Mumimo, Daisy Chain, beamforming, fast roam all disabled.
Orbi in AP mode
ALL devices have static IPs entered into googlefiber Box/modem
multiple reboots performed of every single device
Fresh Firmware installs performed on sattalite and main unit per instructions on forum
Hand input config settings after nvram wipe
Followed procedure to add sattalite
Followed forum instructions to add sattalite
...no matter what I try with this version sattalite does not show as a sattalite but as attached device to the main unit.
Possible that while in AP mode it just shows in the mail list with everything else. Let see if one of the forum moderators can give us some info.
JMU1998 wrote:
I was able to see my sattalite listed as a sattalite in the list on the Main unit before 2.1.4.16 the release prior. Nothing has changed in my setup since then. Orbi RBR50 is in AP mode and I have one satellite wired backhaul. I have a gigabit down/up googlefiber and all my cabling is new cat6 and cat7 high quality. I have a switch s8000 Netgear in the mix.
Mumimo, Daisy Chain, beamforming, fast roam all disabled.
Orbi in AP mode
ALL devices have static IPs entered into googlefiber Box/modem
multiple reboots performed of every single device
Fresh Firmware installs performed on sattalite and main unit per instructions on forum
Hand input config settings after nvram wipe
Followed procedure to add sattalite
Followed forum instructions to add sattalite
...no matter what I try with this version sattalite does not show as a sattalite but as attached device to the main unit.
Folks,
The amount of troubleshooting required to make a consumer plug and play WiFi router work properly in people's homes is staggering. Look at the number of posts in this thread alone, and then the Orbi forums in general. You really only ever see this level of engagement in consumer products in two scenarios:
1. The product has turned into a hobbyist hack friendly product that people are doing all sorts of things it wasn't designed to do, but can.
2. The product doesn't work well and sold a lot based on intial reviews that were positive.
Guess which one the Orbi falls into? Maybe 20 devices connected is a problem (there are some older/cheap wifi routers out there that can't really handle more than 10 devices). Orbi isn't cheap or old. Maybe load is the problem (hope not...). Perhaps it is environmental? Point is, the consumers shouldn't have to spend a lot of time and cycles to beta test Netgear's firmware releases. They should be regression testing this stuff in multiple environments that is representative of what is out in the field. Big houses with at least 20 devices connected and working at a minimum. We are in an IoT age where it is not uncommon to see 20+ devices on a home network.
What I suspect they are doing is they are fixing bugs, testing those specific bugs in a single room with 1 router and 1 sat, and calling it good and pumping out a release. That's not how you test systems. This is how old bugs creep back in and how you get unstable releases. And just because it's working well for Person A doesn't mean it's good. It means Person A's setup is closer to what Netgear is testing against internally. That's it. If they are not testing enough setups/scenarios, then they will never find all issues in the software and it will continue to be a problem.
Of course, it could simply be bad hardware, too. It is quite possible there are batches of bad Obris out there. But given the performance has been degrading over multiple software releases one tends to suspect the software.
