Orbi firmware update v2.1.4.16 availability

Try 40 feet with just 1 satellite.

I would suggest this as well. See if you can get the cable modem moved to maybe the bottom of the U, or you can leave the cable modem where it's at and have someone install a RG46 CAT6A cable run from the cable modem placement, either up in the attic or maybe in the walls and get the end point down around where the buttom of the U is where you could place the main base router, then put 1 of the satllites at either tip of the U. You might ask about running a 2nd LAN cable run from the bottom of the U to either tip of the U and go wired back haul. Something to review.

---

Retired_Member wrote:

The placement is not ideal it's in the upper left portion of the "U".  Not by choice, but due to cable modem access.

 

I've tried 1 satellite (but at more like 150 ft), which was my original setup on the RBR50-V2.1.4.10 firmware, and with RBR50-V2.1.4.16, with the one satellite I was still seeing the network go down.

 

I can/will try with a more closely placed single satellite as you suggest and will also be downgrading to the RBR50-V2.1.4.10 firmware to see what results I get.

 

I strongly suspect a regression in the firmware with wireless backhaul sattelite configurations.

---

Baseman70, good to see you are trying to resolve the problem.  

My experience is that pre Orbi, my Billion modem/router with WiFi functioning was not up to penetrating my inner plaster walls with any great quality, and nor is my Orbi router, so at the end of the house where the Orbi router is located, connectivity is fine, but signal strength is a bit weak, but my wired satellite in an open plan area 10 meters away from the router, is fantastic.  The satellite’s reach is phenomenal - up to 15 meters to a LIFX globe in the garden, at 100% signal strength.  This is why I praise my Orbis.  

Now to your problem, FURRYe38 is on the money with his suggestion of running new Ethernet, but if that’s not possible, you can try a powerline adapter. Here’s some information on that.  Some power line adapters may create interference, but it may be a way to see if there’s sufficient enough improvement to justify the running of cat6 cable.  That’s what I have done, which I think contributes to my successful outcome.  Re powerline adapters, I have a Netcomm power adapter with a bypass power outlet delivering a network point to an out of the way place that’s used occasionally, and it works without any issues I can detect.  My two adapters have 3 status lights that alert me to connectivity issues, which are always green.  

Good luck

My Orbi RBK53 costco system - one of them locked up on 2.14.16 - hard crash, couldn't reset, restart, finally had to full reset using pin and re-set this up.  This is the second time this particular orbi locked up like that.  Complete freeze.  Wifi and ethernet ports.  Only difference is this setup has one ethernet satellite and one wifi satellite.  I remember hearing this was an issue in the past - is it still an issue?  I'm going to run both satellites wireless for now. 

Disable Daisy Chain on the router if your running mixed wired and wireless back haul...

---

cyberprashant wrote:

My Orbi RBK53 costco system - one of them locked up on 2.14.16 - hard crash, couldn't reset, restart, finally had to full reset using pin and re-set this up.  This is the second time this particular orbi locked up like that.  Complete freeze.  Wifi and ethernet ports.  Only difference is this setup has one ethernet satellite and one wifi satellite.  I remember hearing this was an issue in the past - is it still an issue?  I'm going to run both satellites wireless for now. 

---

Update: the thought plickens in my Orbi household!  I downgraded the router and two satellites to V2.1.4.10 last night, reran the tests and the same network outage and crash occurred.

So... I have ruled out a recent regression in the Orbi V2.1.4.16 firmware to be the cause.

In looking at what has recently changed on my network I'm now looking at the products I work on which are also mesh WiFi products that happen to use the very same Dakota radios that are in the Orbi's.

The products I work on are also mesh WiFi products but serve a different IoT related purpose (due to NDA I can not go into further detail).  I have recently added more of these devices to my network.

These products also run firmware and software that is routinely updated as they are under development at this time.

My new theory is that these IoT products (which create mesh network of their own and also heavily utilize multicast) are somehow conflicting with Orbi and contributing to and/or causing these network crashes.

To thest this theory, I have taken most (but not all for specific reasons) offline for the day to see how the network behaves.  I have also updated the Orbi's back to V2.1.4.16.

If I can prove a strong correlation between our products being on the Orbi network and the network going down that will be interesting.

It could be that other devices creating a mesh is causing issues or very heavy multicast traffic.  Multicast is definitely an area that Orbi has been working on improving.

I'd love to be able to discuss this in more detail with some Netgear engineers.

But since this topic no longer seems to be directly related to the V2.1.4.16 firmware specifically, I'll probably start a new thread.