Announcing availability of OrbiOS 2.1

2.0.0.74 has terrible connectivity issues. 2.1.1.12 just made them worse. I hear the 1.x versions are fairly stable. However, I also hear that they have some major security bugs which were patched in the newer versions. I'd be rather concerned about using 1.x and leaving my home vulnerable to hacking.

Doesn't appear to fix the display of attached devices as advertised... it showed up for 3 hours after the update, now is consistently empty on my satellite.  Am certain there are devices connected to the satellite.

---

kmichalec wrote:

---

CattleDog wrote:

I applied 2.1.1.16 and it appears to have fixed the issues I was having (its been about 8 hours so far).

---

Which issues were you having exactly, and what FW version did you upgrade from?

---

Loss of connectivity about once every hour or two.  Would typically last 5 to 10 minutes.  I have two satellites.  One disappeared (no longer seen as a connected satellite).  The other seemed ok, but suffered the same drop out issue (probably coming from the router).

I was fine and stable on 2.0.0.74 on all 3 devices (RBR50 and 2 RBS50).  I manually applied the 2.1.1.12 update to the router and it all went to hell.  The satellites would never take .12 manually.  After a few days, I rolled the router back to 2.0.0.74, but the issues remained.

I am now on 2.1.1.16 on all 3 devices, and everything is working as expected (I had to manually re-add the one satellite). 

---

aaz wrote:

---

dmw_2 wrote:

.. Everything seemed rock solid so I decided to try the ethernet backhaul to one of my RBS50 satellites.  Within moments of plugging an ethernet cable into one of the LAN ports of the satellite and the other end into a remote switch located near the satellite the network just went into a cycle of crashing...  

---

What kind of switch do you have connected to the satellite and what plugs into that switch? Do you really need more ports there than the satellite can provide?

Also maybe try using ethernet backhaul through the switch instead of connected directly to the satellite if you can.

Thank you tagteam for directing me to that diagram about how ethernet backhaul can be set up.  I am not sure if it's critical to have the RJ45s plugged into those exact LAN ports but the diagram with the SWITCH best matches my set up.  However, with the Orbi coming so long after me laying concealed ethernet cables around my house over time, there are in fact 3 switches involved before the satellite.  Within a few inches of the RBR50 there is a Netgear GS308 which primarily serves all the devices round my PC workstation.  One of the ports on the GS308 is then hard wired round to a cupboard and a Netgear Pro Safe GS116 (that provides ethernet to various hubs e.g. British Gas HIVE, a weather station, a NAS (Netgear ReadyNAS 212) etc.  One of the ports on the GS116 then goes out to the garage and a TP Link PoE switch which connects to several wildlife cameras, IP cameras and micro PC used as a camera server.  One of those TP Link ports is where I plugged the RBS50 into.  Now, responding to aaz's question ... the garage is right on the limit of backhaul signal and shows as 5G but POOR (probably 25 feet but 3 brick walls away).  As the ethernet cable is already in situ I thought it made sense to use that for the backhaul but it cannot be used exclusively by the RBS50.  It's possible I could plug the ethernet cable from the GS116 into the garage into the RBS50 and then put the TP Link switch beyond it (thus reducing to 2 switches between the RBR50 and RBS50) but whether that would solve my crashing network problem I do not know without trying.  I hope my explanation of my network topology makes sense.