NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
packetwerks
Apr 02, 2018Star
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?
packetwerks
Apr 02, 2018Star
Factory reset router and satellites. I wasn't able to reload the old config as it would make the router disappear from the wired side (e.g. it's old static IP wasn't reachable). So treated it like a new install. Got all satellites sync'd but one wouldn't use wired backhaul - only 5Ghz. So now trubleshooting that.
FURRYe38
Apr 02, 2018Guru - Experienced User
OK, swap satellites around to see if the problem tracks or not..
- packetwerksApr 02, 2018Star
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.- FURRYe38Apr 02, 2018Guru - Experienced User
No doesn't matter. Switch will route the traffic the same way on any LAN port.
- packetwerksApr 02, 2018Star
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 eth1
Wired 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 no
Any idea why one satellite would start with different interfaces?