NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Please, Please, Please add "Force Ethernet Backhaul" to settings!!
I love my Orbi system (Router + 2 Sats) but the inability to force ethernet backhaul is such a pain. If the power flickers, all devices reboot and will try to reconnect. Since the router takes a bi...
I did another emulated power cycle. ARP storm happened again with the RBS connected via ethernet with LAN switch, seems to go about 1 minute or a bit longer this time however stopped and the system continued working fine.
I thought maybe having the web page opened on the RBRs web page was contributing to this but no, happens with the browser closed. Seems that a power outage then back on will trigger the storm however only seems to last for about a minute then stops.
Ozymandias_EBON wrote:
If the power flickers, all devices reboot and will try to reconnect.
If this happens frequently, it might be worth investing in some small UPS units. All of my network devices are powered through UPS to avoid just this sort of thing. (No help when Edison cuts power for eight hours, but that is fewer than two times a year.)
I found a workaround that minimizes the network loops created by the satellites.
To reiterate, the real solution would be a setting where you can select backhaul priority.
1) Wireless Only (Default)
2) Ethernet Only
3) Ethernet First / Wireless Second
Netgear should change the method the satellites connect as the current method causes network loops.
Back to the workaround...
1) All devices powered off.
2) Power on satellites
3) Wait until ALL satellites show ethernet activity (it takes about 30-45 seconds for each)
4) Power on Router (main unit).
I had another power flicker yesterday.
Using this process I was back up completely in about 5 minutes with no loops.
And for good measure, I did pick up some UPS's for the satellites.
Ethernet backhaul works as intended. Only factors that can cause problems are bad or incorrect CAT# cableing, bad cabling plugs or jacks or bad patch panels, use of managed switches that haven't had there IGMP protocols and green ethernet features disabled. Seen some non managed off branded switches cause problems as well. Not all switches are the same.
NG GS-105/108v4 and GS308v3, D-Link DGS-105/108 and HP ProCurve 1400/1800 series switches work for Orbi systems. XS505M and GS110MX work great with the 9 series.
There would be no reason for force ethernet backhaul. And besides NG keeps the system set for automatic configuration so if something does happen on the ethernet connection, the RBS can fall back to wireless backhaul.
Alas, I fear it would be nearly impossible to convince Netgear engineers that their design is incorrect. They have sold 10's of thousands of Orbi units and this is not a common experience. That being said.....
The work-around solution appears backward to me.
Ozymandias_EBON wrote:
Back to the workaround...
1) All devices powered off.
2) Power on satellites
3) Wait until ALL satellites show ethernet activity (it takes about 30-45 seconds for each)
4) Power on Router (main unit).
If the problem is caused by the Satellites coming up first and not seeing the router Ethernet connection, then it seems to me that the word-around would be to
- Power off the satellites. (Leave the router alone).
- Say a prayer (or sing Happy Birthday).
- Power up the satellites.
Yes, it does seem backward which is why I never tried it before.
Based on what I can discern from the top light on the satellite, and the lights on the switch...
Top light goes solid...15-20 seconds later activity starts on the switch.
It "appears" the satellites wireless radio starts first and then the wired connections starts after.
The satellite wireless detects the wireless router and starts config sync.
15-20 seconds later the wired connections connect and starts config sync.
During this time is when the network loop is detected and all hell breaks loose.
By NOT having the Router on, AND waiting until the wired connections startup, the satellites are left in limbo.
Once I power on the router, the wired connection starts up first, the sat's wired starts config sync before the wireless can connect... no network loops.
It's good that you have a recovery method that works for you. The UPS units should help reduce the number of times per year this might happen. I can't help but wonder if this is somehow related to the specific model of Orbi system or to the switches.
The original Orbi (2016) did not support wired backhaul. The feature was introduced in a firmware update. It is now been a feature for quite some time. It seems (to me) that if this is an across the board issue with all Orbi systems, then any user who has satellites connected with wired backhaul would face this issue on every power outage.
Actually, it seem that the act of simply powering up a satellite that has a wired backhaul would immediately create a loop storm and this could be done at will. Power up. Storm. Power off. Power up. Storm. etc. etc.
My impression is that the router has a timer that checks periodically, "is there a satellite on the LAN?" When it finds one, the backhaul changes from WiFi to wired. If the router says, "damn. it's gone.", then backhaul switches to WiFi. Both backhaul links would have to be up and running at the same time to create a loop. I cannot imagine what tools it would take to document what is going on. The WiFi connection is encrypted, but the Ethernet connection may not be. I guess running Wireshark simultaneously on both the Ethernet and WiFi connections would show if there is traffic on both at the same time.
This is yet another occasion that I wish my house was "wired".