NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBS50 wired backhaul stopped working and messing up internet
I've had the RBS50 and 2 satellites running without issue for several months until today. The satellites are connected with ethernet cables for wired backhaul.
Came home from dinner and wireless network is down. Spent a long time searching for the issue and found out that when I disconnected the ethernet cable from one of the satellites, the network came back up. The other satellite has no issues with wired backhaul.
Can anyone help? Network is fine if the rogue satellite doesn't have the ethernet cable plugged in.
Firmware version is 2.5.2.4
Daisy chain enabled
Main router is an Asus AC 3200 and running orbi RBS50 as AP mode
Funny that it would be fine for months and suddenly now have an issue.
Came home from dinner and wireless network is down. Spent a long time searching for the issue and found out that when I disconnected the ethernet cable from one of the satellites, the network came back up. The other satellite has no issues with wired backhaul.
Can anyone help? Network is fine if the rogue satellite doesn't have the ethernet cable plugged in.
Firmware version is 2.5.2.4
Daisy chain enabled
Main router is an Asus AC 3200 and running orbi RBS50 as AP mode
Funny that it would be fine for months and suddenly now have an issue.
5 Replies
Are the RBS ethernet connected directly to the back of the RBR or is there a switch in the mix? What is the Mfr and model# of the ethernet switch in the configuration?
https://kb.netgear.com/000051205/What-is-Ethernet-backhaul-and-how-do-I-set-it-up-on-my-Orbi-WiFi-SystemTry swapping RBS with each other to see of the problem follows?
Is Daisy Chain enabled or disabled?
Has a factory reset and setup from scratch been performed since last FW update?
I found that v4 causes ARP storms when RBS are ethernet connected with switches in the mix.
- Thanks for trying to help.
- I do have a netgear 308 switch between the wall and the orbi.
- Daisy chain is enabled (should this be disabled? Read some threads about this and not entirely sure what setting it should be in).
Well, after a sleepless night trying to sort this out, I finally decided to turn off everything in the house. Literally anything that had an Internet connection.
Turned on everything one by one, and found out that the Sony sound bar connected to the satellite was the culprit. As mentioned in first post, every time I disconnected the ethernet cable to the satellite, my network would be restored. Decided to try disconnecting the lan cables on the back of the satellite one by one, and that's when I found out it was the sound bar.
I did a reboot of the sound bar and re-initialized its ethernet connection. And after that everything became back to normal.
Not sure what happened in between the afternoon and dinner time. Perhaps a power trip or some ip address conflict.
Goodness can't believe I spent hours and hours trying to sort this out...
Roasty wrote:
Thanks for trying to help.
- I do have a netgear 308 switch between the wall and the orbi. Can you remove the switch and directly connect the RBS to the wall jack and see?
- Daisy chain is enabled (should this be disabled? Read some threads about this and not entirely sure what setting it should be in). Yes.
Well, after a sleepless night trying to sort this out, I finally decided to turn off everything in the house. Literally anything that had an Internet connection.
Turned on everything one by one, and found out that the Sony sound bar connected to the satellite was the culprit. As mentioned in first post, every time I disconnected the ethernet cable to the satellite, my network would be restored. Decided to try disconnecting the lan cables on the back of the satellite one by one, and that's when I found out it was the sound bar.
I did a reboot of the sound bar and re-initialized its ethernet connection. And after that everything became back to normal.
Not sure what happened in between the afternoon and dinner time. Perhaps a power trip or some ip address conflict.
Goodness can't believe I spent hours and hours trying to sort this out...
