NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
v2.1.3.4
My Orbi autoupgraded to v.2.1.3.4 this morning and I found tht ethernet backhaul no longer works. Is this expected behavior? Anyone else seeing this?
OK, swap satellites around to see if the problem tracks or not..
I'll give that a try.
Question: Does the LAN port on the back of the router and/or satellite matter for wired backhaul? Out of habit I always put the connection to my switch (what I want to be the backhaul) in the LAN port closest to the power plug.
No doesn't matter. Switch will route the traffic the same way on any LAN port.
I can't move the sat now but I did notice that two identical (hardware) satellites have different interfaces:
Wired Backhaul working:
bridge name bridge id STP enabled interfaces br0 8000.9c3dcfe5a291 no ath0 ath01 ath02 ath1 ath2 ath21 eth0 eth1Wired Backhaul not working:
root@RBS50:/# brctl show bridge name bridge id STP enabled interfaces br0 8000.9c3dcfe58e41 no ath0 ath01 ath1 ath2 eth0 eth1 brwan 8000.000000000000 noAny idea why one satellite would start with different interfaces?
Where is
8000.9c3dcfe58e41
connected too? Directly to router or 1st Sat?
Is Daisy Chain enabled or disabled?
I would test this one Sat alone directly with the router, with the others turned off temporarily and see what happens.