I have upgraded my Orbi router and satellites to the latest firmware (2.1.2.18) and I am seeing some weird behavior with regard to what's shown on the "Connected Satellites" section of the orbi router. Mainly I am seeing one of my satellites refuse to connect using the ethernet backhaul, giving me poor dl/ul performance when connected to that satellite. It is plugged directly into the same switch as all the other satellites and router, and the ethernet cable to the switch is plugged into the leftmost Orbi satellite port (not sure if that matters or not) but for some reason it always connects over 5G. Unfortunately 5G doesn't work well in my house due to the walls and shape of the house, which is why I had ethernet run in the first place. The second satellite, plugged into the same switch, connects correctly over ethernet backhaul, but displays a really weird IP address, one that shouldn't be possible in my network (my router only assigns IPs from 192.168.0.X). When my phone connects to that satellite performance is excellent and it's IP seems normal (192.168.0.193). Maybe there's just something screwed up with the display in the router page? This must be the case since I can directly connect to that satellite at 192.168.0.177. Is there an option to force a satellite onto ethernet or is this just a bug that is causing the satellite to fall back to 5G? I know the ethernet port/switch works fine since I can connect my PC directly to it and get great speeds. Here's a picture of what my router is showing for the two satellites:

I decided to write an updated version of the Orbi (and Orbi Pro) STP (Spanning Tree Protocol) instructions. This is for users who have managed switches and trying to use Orbi Ethernet Backhaul. Those with unmanaged switches should not have any problems with Ethernet Backhaul. Orbi uses Classic STP. Do not try to use Rapid STP. Hopefully Netgear will change this in a future update. Orbi uses the default STP Priority (AKA: ID) of 32768. Orbi does not allow any modifications of STP settings. Again, hopefully they will change this in the future, at minimum they should Allow Orbi STP to be disabled for those with managed switches. Your L2 managed switch should have STP Enabled. Again, use Classic STP should you have a choice between STP and RSTP. Orbi is STP only. All switches in you LAN “MUST HAVE” an STP Priority of 32768. Do not change your STP priority or Orbi Ethernet backhaul will not work properly. AKA: It may work, then break and cause other undesired problems. Using an ID higher priority than Orbi will cause your switch to STP Block/discard the Orbi Satellite ports, forcing the Satellites into WIFI Backhaul mode. Using a lower priority STP ID will allow Orbi to take STP Root Bridge role and most likely create loops and crash your LAN. Plus, any network nerd who cares about security, stability and visibility DOES NOT want Orbi becoming a root bridge of the LAN. Using 32768 allows each switch (both Orbi and your switch) to become their individual “root bridge” for STP and prevents Orbi and your switches going to WAR and arguing “who has control”. Your Main Orbi Router (using AP or Router mode) must have STP enabled on its switch port with NO MODIFICATIONS. STP, Auto-Edge, Default Cost, etc, etc…no changes….. ALL ORBI SATELITES USING ETHERNET BACKHAUL MUST HAVE STP ENABLED….BUT…. Edge Mode must be forced “ON”. AKA: Port Fast mode ON. I know some network nerds are thinking…”Why would I force an STP BPDU device to use PortFast mode?”….Simple answer…Orbi is using Classic STP and Auto-Edge (AKA: Learning Mode) will take too long and your Orbi Satellites will give up and switch to WIFI Backhaul. After that…you are screwed and must reboot your satellites…or wait 15-20 minutes for Orbi Satellite to “hopefully” try again. Classic STP is SLOW and your Orbi Satellites will need to wait 20-60 seconds for STP to decide if the connection should be allowed…which is why Rapid STP was created YEARS AGO…..Why Netgear is using Classic…I don’t know. DO NOT DISABLE STP!!! Doing this will cause a network loop and most likely crash your network. Even though you are forcing the Satellite ports to use PortFast Mode (AKA: Edge Mode Enabled…Not Auto). STP will still serve its basic function and protect against network loops. If you disable STP on the Satellite ports….No protection and Orbi will create a loop. That’s is. Using this config should allow your Satellites to use Ethernet Backhaul with minimal problems via manages switches. Orbi does take a few minutes to determine what path to use. So don’t expect instant results. Give Orbi 5-10 minutes and check the Satellite connection status. If Your Orbi is rebooted it “should” go back ed wired mode after a few minutes. But, without a proper STP configuration as described above….NO CHANCE….Or very unstable results. Shame on Netgear for not allow STP Enable/Disable. Especially for Orbi Pro.

If your router is working in AP mode, be sure to connect it to the switch using the first LAN port and not the router port. If your LED ring stays a solid magenta afterwards… this seems to be a bug in the Orbi firmware. I switched the LED ring off, since this cabling is also the way Netgear has stated on their support site on how to connect the satellites via ethernet.In this setup, either the satellites as well as the devices connected wirelessly to the satellites are displayed correctly on the Orbi's web page.

So I definitely had the router plugged into the WAN port still even though it was in AP mode. I moved the cable over to the leftmost switch port on the RBR50 and now I'm really getting weird behavior. Internet access from the RBR seems to be working fine, however both satellites now show up as 5G... at least they now both have the correct IP addresses. In addition, any devices connected to those satellites have no internet access and are having issues connecting to local nodes as well. Let me try resetting everything and starting over to see if that fixes anything.

So I did a hard power-on reset and then disabled daisy chain topology and one satellite is now up and running on wired but the other is still forcing itself onto 5G. What gives? Netgear, if you're listening, it would be great if you could have an option to select the backhaul to use. Eg Auto, ethernet, 5g. That was some of us could force a specific satellite onto ethernet when these weird cases crop up and the satellites don't seem to use the faster backhaul.

Throwing out obvious questions, have you verified the cable to that satellite is good, no faults? Any way to check it or substitute a different cable to make sure? Same for switch port?

Orbi RBK53 ethernet backhaul issue

17 Replies

budy
Luminary
Feb 13, 2018
If your router is working in AP mode, be sure to connect it to the switch using the first LAN port and not the router port. If your LED ring stays a solid magenta afterwards… this seems to be a bug in the Orbi firmware. I switched the LED ring off, since this cabling is also the way Netgear has stated on their support site on how to connect the satellites via ethernet.
In this setup, either the satellites as well as the devices connected wirelessly to the satellites are displayed correctly on the Orbi's web page.
- dalnew
  Tutor
  Feb 13, 2018
  So I definitely had the router plugged into the WAN port still even though it was in AP mode. I moved the cable over to the leftmost switch port on the RBR50 and now I'm really getting weird behavior. Internet access from the RBR seems to be working fine, however both satellites now show up as 5G... at least they now both have the correct IP addresses. In addition, any devices connected to those satellites have no internet access and are having issues connecting to local nodes as well.
  
  Let me try resetting everything and starting over to see if that fixes anything.
  - dalnew
    Tutor
    Feb 13, 2018
    So I did a hard power-on reset and then disabled daisy chain topology and one satellite is now up and running on wired but the other is still forcing itself onto 5G. What gives?
    
    Netgear, if you're listening, it would be great if you could have an option to select the backhaul to use. Eg Auto, ethernet, 5g. That was some of us could force a specific satellite onto ethernet when these weird cases crop up and the satellites don't seem to use the faster backhaul.
MillerHouseTX
Tutor
Jun 08, 2018
I have this exact issue... Please help
- FURRYe38
  Guru
  Jun 08, 2018
  https://community.netgear.com/t5/Orbi/Steps-to-reproduce-the-Orbi-backhaul-issues/td-p/1516065/jump-to/first-unread-message
  
  MillerHouseTX wrote:
  I have this exact issue... Please help
  - Flash008
    Luminary
    Jul 27, 2018
    Well, if it helps anyone sleep better…
    
    20 year I.T. nerd who just jumped on the Orbi train. Like many, I wanted Ethernet Backhaul and had problems.
    
    I DO USE CISCO MANAGED SWITCHES!!!!
    
    After a few hours of troubleshooting I found my problem.
    
    FIRST…If you don’t understand STP (Spanning Tree Protocol)…..then go read…I am not teaching STP tonight….It’s too late and I am tired.
    
    I can confirm Orbi (and Orbi Pro) are using STP (NOT RSTP)…What a joke…who doesn’t support Rapid STP today…LOL…I managed to confirm this by changing my STP ID (Prioroty) on my Cisco switch to 61440…AND GUESS WHAT???? My root bridge ID (AKA: MAC) changed to the ORBI ROUTER….This is only possible if Orbi is running STP and has an ID higher or the same ID as my Cisco. I typically use ID=0 for my Cisco….Which would explain the problem.
    
    Orbi wants control of STP…..It’s that simple….And Netgear offers no method to change ANY STP settings in their code….Hence your managed switches with STP will go to WAR with Orbi and make Ethernet backhaul nearly impossible.
    
    STP rules my friends…Highest STP ID WINS! It’s just how STP is designed.
    
    Furthermore. If you have a managed switch with a higher STP ID (Priority), then every time Orbi attempts to change (update) the typology (such as switching from WIFI to Ethernet backhaul)….GUESS WHAT…..Can you say “discarding/blocked state”.
    
    What’s more FUN…is the Satellite that is connected via ethernet now has its port set to discarding….This is forcing the satellite to use its WIFI backhaul and my Cisco switch is “discarding all packets from that Satellite Ethernet port.
    
    So now….My ONLY option is to….DISABLE STP on my satellite port. This will allow a LOOP. BAD!!!!
    
    But I must put my TRUST into Netgears hands….and hope the code is smart enough to send all client MACs down the ethernet port and not the WIFI port…God knows if my switch STP sees MACs coming from both the Sat ethernet port and the main Orbi router ethernet port (which will happen if clients MAC take both paths via the WIFI backhaul….)….well….we network nerds know what happens then….LOOP…DISGARD all packets….or broadcast storm (should you disable STP) and your entire LAN crashes…..
    
    So, my config I am rolling with is….STP enabled on my Cisco (only STP, not RSPT…Orbi doesn’t support RSTP…STUPID)…..
    
    Disable STP on Satellite ports….This allows MACs to take both ethernet and WIFI backhaul paths.
    
    Insure STP is enabled on the Main Orbi router ethernet port. AP mode or Router mode, doesn’t matter. This will protect you from a packet loop crash.
    
    This config will allow your Orbi Sat to ALWAYS be able to communicate with the main Orbi regardless of STP status. After that…its entirely up to the Orbi Sat to establish its ethernet backhaul….a reboot will surely be required as the Orbo code is REALLY STUPID…..My GUESS is the Orbi detects Ethernet during boot and if it can contact the Main Orbi via Ethernet…then it prefers that connection and will switch-off the 5Ghz backhaul which I confirmed by logging into the Sat directly and observing the 5Ghz backhaul DISBALED when using ethernet…
    
    But, if that Ethernet drops and Orbi Sat can’t communicate with the main Orbi (due to STP blocking, power outage or other reasons..)…it rolls back to 5Ghz backhaul and doesn’t seem smart enough to switch back to ethernet….without another reboot. Again…stupid….
    
    Hoped this helped those with managed switches and using Orni with ethernet backhaul.
    
    Surely Netgear could have done this better….
    
    An EASY fix would be for Netgear to allow STP to be DISABLED and let our managed switches handle STP….
    
    And really…RSTP would fix this easily….Why are you not using RSTP?….Do you have any idea how long it takes classic STP to update topology when connections change….REALLY….??????
    
    I spent 10 minutes looking at my RSTP stats…then it hit me….My Orbi ports shows STP….NOT RSTP mode. I tried to force an RSTP migration…But nope…Your Orbi’s kicked by STP mode back to classic….LAME!!!!

Forum Discussion

Orbi RBK53 ethernet backhaul issue