NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
Did you try a reboot of the system or full factory reset and set up from scratch after it updated to v2.1.4.10?
Oceanwaves wrote:
Update: Exactly 1 hour after downgrading RBR20 and RBS20 to 2.1.2.18 the router was updated to 2.1.4.10 again :smileyfrustrated:. I disabled Daisy Chain and both Orbis rebooted (satellite was still on 2.1.2.18). The status page showed "wired" and the backhaul status switched between "Connected" and "Bad". A few minutes later the satellite was automatically updated to 2.1.4.10, too.
Network was down again.
That's it. I need my LAN as I'm working from Home Office today. I switched the Orbis off and activated the WiFi on my ISP's router again.
Does anybody know whether the Google WiFi or Ubiquiti support Ethernet backhaul and AP mode for the router?
FURRYe38 wrote:
Did you try a reboot of the system or full factory reset and set up from scratch after it updated to v2.1.4.10?
Yes, that didn't help. As soon as I plug in the Ethernet cable into the AP or the satellite, the network ist down. UPS looses connection to NAS, PC looses internet connection and NAS connection and so on.
However, did another try with 2.1.2.18 as I got a hint for another nvram option:
nvram set orbi_auto_upg=0
This was still set =1, so at least for the RBR20 there are 4 options that have to be set.
Let's see if this helps to fix the auto update. And then wait fo a working FW.
How long are you waiting after you plug in the ethernet cable? 5 minutes is needed for the system to reconfigure for wired back haul. Do you get a BLUE LED on the satellite?
Disable Daisy Chain as well.
Is there a network switch in between the router and satellite? If so, whats the Mfr and model of the switch?
Reivew this:
FURRYe38 wrote:
How long are you waiting after you plug in the ethernet cable? 5 minutes is needed for the system to reconfigure for wired back haul. Do you get a BLUE LED on the satellite?
Disable Daisy Chain as well.
Is there a network switch in between the router and satellite? If so, whats the Mfr and model of the switch?
Reivew this:
Well, when I downgraded to 2.1.2.18 again yesterday I followed that procedure. I started the satellite without ethernet and let it run for 15-20 minutes. After that time the light was off. But I usually get a bad connection at 2.4 GHz with WiFi backhaul because of an armored-concrete ceiling. The distance between AP and satellite is around 2 meters. The problem is the ceiling. That's why I have a CAT7 cable between 1st and 2nd floor.
I tried that procedure with 2.1.4.10 also, but as soon as I plug in the ethernet cable my network goes down within 30 seconds. The lights on the switches are flashing in sync and I notice a lot of package drops when doing a ping.
I also disabled Daisy Chain, Beamforming, MU-MIMO and Fast Roaming, which didn't help.
I have 2 switches between RBR and RBS20. They are both D-Links (DGS-108, 8 ports 1 GBit simple switches).
As both devices are currently running 2.1.2.18 and everything seems stable, I will wait for a new FW before doing more tests. Only drawback at the moment is that the "Attached devices" page looks strange. For example it says that the the satellite is connected at 5 GHz and the backhaule status is bad (in fact it's connected to ethernet). And my Android phone is connected by wire to the satellite. But I'm next to the router and there's definitely no cable coming out of the phone... The devices list was ok before the last automatic update to 2.1.4.10 yesterday.
Ok, sounds like you got it running better. Glad the linked URL helped. Seems to be a good process.
Just checking to make sure you don't have any managed switched in the mix. Seem to have issues between Orbi and managed switches.
Oceanwaves wrote:
FURRYe38 wrote:
How long are you waiting after you plug in the ethernet cable? 5 minutes is needed for the system to reconfigure for wired back haul. Do you get a BLUE LED on the satellite?
Disable Daisy Chain as well.
Is there a network switch in between the router and satellite? If so, whats the Mfr and model of the switch?
Reivew this:
Well, when I downgraded to 2.1.2.18 again yesterday I followed that procedure. I started the satellite without ethernet and let it run for 15-20 minutes. After that time the light was off. But I usually get a bad connection at 2.4 GHz with WiFi backhaul because of an armored-concrete ceiling. The distance between AP and satellite is around 2 meters. The problem is the ceiling. That's why I have a CAT7 cable between 1st and 2nd floor.
I tried that procedure with 2.1.4.10 also, but as soon as I plug in the ethernet cable my network goes down within 30 seconds. The lights on the switches are flashing in sync and I notice a lot of package drops when doing a ping.
I also disabled Daisy Chain, Beamforming, MU-MIMO and Fast Roaming, which didn't help.
I have 2 switches between RBR and RBS20. They are both D-Links (DGS-108, 8 ports 1 GBit simple switches).
As both devices are currently running 2.1.2.18 and everything seems stable, I will wait for a new FW before doing more tests. Only drawback at the moment is that the "Attached devices" page looks strange. For example it says that the the satellite is connected at 5 GHz and the backhaule status is bad (in fact it's connected to ethernet). And my Android phone is connected by wire to the satellite. But I'm next to the router and there's definitely no cable coming out of the phone... The devices list was ok before the last automatic update to 2.1.4.10 yesterday.