NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Problem of newly added Orbi ethernet backhaul
I am using a RBR50 as my main router connecting to two satellites wirelessly in daisy chain like this:
RBR50 <==> RBS50 <==> RBW30
In order to extend my wifi signal, I bought a new RBS50 and try to configure it using ethernet backhaul (at the place where wireless signal poorly reached). I have it wired directly to one of the LAN port of my existing RBR50 router then power it on. At the very beginning it seems to work fine. On the admin page I could see it appeared under "Attached Satellites" and the connected Orbi is RBR50 wired (but also wireless occasionally).
However, after a minute or two, most of my wired devices lost Internet connection. Those wired devices are connected to a 24-port unmanaged netgear switch which connected to another LAN port of that existing RBR50 router. I checked the admin page again and found that the "connected Orbi" of those wired "Attached Devices" have been unexpectedly changed to my newly added RBS50 Satellite!! It get back to work only when I turn it off so that the devices connect to the router again. I confirmed that all my devices have upgraded to latest firmwire 2.1.4.16.
Before netgear introduce ethernet backhaul feature to Orbi, the satellite only connect to router wirelessly and the LAN ports was to provide wired LAN access to a wireless network. Now that they introduce ethernet backhaul feature, the usage of their LAN ports become ambiguous. On one hand it use the port for ethernet backhaul communication; on the other hand it draws my wired device from the router, like it is connected to router wirelessly in the old day. I wonder if there any way I could force the satellite to 1. stop acting like a router gateway, and/or 2. disable wireless backhaul (so no auto switch between wired and wireless). Any ideas on how to get it works?
Thanks in advance!
16 Replies
You can try disabling Daisy Chain and see. I don't know if this will work. I know for most wired back haul configurations, Daisy Chain needs to be disabled. Also not sure if your configuration is supported. Most satellites have to be directly connecte to the base router or thru a non managed switch to the base router. I don't know if daisy chaining from a wireless connected satellite to a wired connected satellite is supported.
I have daisy chained topology turned off and my ethernet backhaul has been broken for most of this year. It was supposed to have been fixed, I believe, in a recent firmware update but I don't see any difference. Looking to move to another system due to this bug. Funny thing is that it used to work.
I also had issues with Ethernet Backhaul that I later found out to be caused by my wired speakers to the Orbi Satellite.
Do you have any wired speakers (connected to the LAN ports of the Router/Satellite)? Any other wired devices?
My Ethernet Backhault works fine for me now.
When I first setup my Orbi network, wifi backhaul worked fine and I was getting 90 Mbps internet speed from my connected devices. When I changed to a ethernet backhaul all my network had issues, and my internet speed dropped to 20-30 Mbps. I kept changing from wifi to ethernet backhaul and back and the issue was consistent. I thought I had the latest firmware version (2.2.1.210) because the online update feature in the orbi admin panel said I had the latest firmware.
It was only when I looked into this further and found there is a more recent firmware (2.3.0.32) that can only be installed by a manual update. Even more confusing was that you first have to manual update to firmware 2.2.1.212 before you can then manually update to 2.3.0.32. (see netgear download page)
Anyway, once I updated to the latest firmware the ethernet backhaul works fine, with no network issues and no loss of intenet speed.
The reason you had to update to an intermediate firmware is because the original firmware limited the size of an uploaded firmware image. When .28 and .32 came out, they were larger than that original size, so they had to modify the limit and the only way you could do that was through (yet another) firmware update.
Glad to hear your issue appears to be resolved. They did a lot of work on the backhaul system in the .32 version.
Glad it's working. Yes the intermediate v212 is needed for the RBR only. You can directly update the RBS to v32.
Enjoy.
Flukey wrote:
When I first setup my Orbi network, wifi backhaul worked fine and I was getting 90 Mbps internet speed from my connected devices. When I changed to a ethernet backhaul all my network had issues, and my internet speed dropped to 20-30 Mbps. I kept changing from wifi to ethernet backhaul and back and the issue was consistent. I thought I had the latest firmware version (2.2.1.210) because the online update feature in the orbi admin panel said I had the latest firmware.
It was only when I looked into this further and found there is a more recent firmware (2.3.0.32) that can only be installed by a manual update. Even more confusing was that you first have to manual update to firmware 2.2.1.212 before you can then manually update to 2.3.0.32. (see netgear download page)
Anyway, once I updated to the latest firmware the ethernet backhaul works fine, with no network issues and no loss of intenet speed.
