NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AmitR
Apr 24, 2018NETGEAR Employee Retired
OrbiOS 2.1.4 availability
A quick update. We're about to release an updated version of OrbiOS 2.1.4 in the next few days through our auto-update mechanism for all Orbi models. When it goes live, you should see a prompt in t...
SwedBear
Apr 29, 2018Tutor
My experience in short: It might be the combination of Daisy Chain and wired Ethernet that is the issue. it seems it was for me. Oh, and also - DO NOT AUTOUPDATE, expecially not with known issues with 2 or more satellites.
------------
I have 1 RBK50 and two RBS50. Both satellites have been using wired ethernet backhaul. Up until yesterday everything worked fine. I was running 2.1.3.x beta and had no big issues. The only thing I can remember is my wife complaining a few times her iPhoneX have some issues keeping a connection but every other Apple-product (4 iPads) have had no issues.
Speeds around 800-900 Mbps via wired (I got 1 Gbps fiber) and my Mac Book Pro easily gets around 500-600 Mbps via WiFI.
This morning my son wakes me up at 6 AM saying the Internet is down. I let him use my phones network via hotspot and started investigating later in the morning.
I noticed that after I turned both satellites off Internet worked again.
I factory reset both the router and the sateliites (I didn't actually notice the firmware had been updated but guessed I had to restart from scratch to find the issue) and set up both satellites via WiFI. Everything worked fine.
I took one of the satellites down to the garage and hooked it up to Wired Ethernet. Everything seems to work fine. I then hooked up the 1st sateliite that is in our livingroom to wired ethernet since "why not. I have ethernet there so might as well use it". In a minute or so the admin showed this satellite also was wired. And then the whole network went down. Could not access admin via wired connection.
Removed the wire and let the satellites use WIFI again: the network came up again.
While writing this I rememebered people talking about Daisy-chain. Sine I do not use it (I might later as I want to place a satellite in a room that is close to the garage but far from the router and which has so-so coverage) I turned it off. Router and satellites rebooted and I then hooked the second satellite up to wired ethernet again. And this time the network has not gone down.
I'm going to continue monitoring the network to see if it continues to stay up.
As for auto-update. I find it inexcusable. In my situation I had the time and opportunity to go through and set everything up again. However, I also have a RBK30 Orbi network in our "summer-house" where also one of my backup-NAS are situated. If that one goes down I will not be able to get to there until in a few weeks. The idea that you push out a firmware update that has KNOWN issues with 2 or more satellites is absurd to me. And the amount of people posting here about the issues they've had from the auto-update show that it really is not a good idea. I test a lot of network stuff and no other router I've used and tested has auto-pushed a firmware. The router is simply to important piece to accidently bring down via an autoupdate.
Elofi
Apr 29, 2018Tutor
I have tried what you said "SwedBear" and it is working so far. I guess this is the soluition for the firmware, for who is using wired to connect to satallite, the new firmware will enable the daisy channing which enable the poor signal over the wired connection, and this is what created the bug.
Good luck everyone :)