NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBS850 - How to prevent 'wired' backhaul via Sonos
My Orbi RBR850 and two RBS850 with Sonos Boost connected to RBR850 runs perfect. To increase SonosNet coverage outdoor I connected a second Boost to RBS850. This temporarily did run perfect, boosting ...
Sonos Boosts are -- supposedly -- just a Sonos speaker "guts" without the speaker -- making it a bidirectional relay.
You can achieve the exact same desired effect by replacing the boost with a Play One.
I wonder if the issue is actually a Sonos issue and not an Orbi one. Have you engaged Sonos about this at all?
Can you try one more experiment?
Move a Play one temporarily to where the Boost is -- hard wired -- and disconnect the boost. The play one SHOULD feed SonosNet (allowing other speakers to work) -- but does it drag down backhaul?
Then do the same experiment without it being hard wired -- e.g. remove the ethernet cable from the Play One.
Two further experiments and a conclusion. When replacing the wired BOOST by a wired speaker, the network matrix shows a clear difference between the first and the matter. A wired BOOST is classified root bridge and speakers get priority to wirelessly connect the BOOST. A wired speaker may stay secondary or tertiary node, and other speakers do not wirelessly connect the wired speaker with priority. The backhaul issue exists with wired BOOST devices as well as with wired speakers. In a second experiment I wired a speaker in the S1 network that does not run SonosNet. This keeps the Orbi WiFi backhaul alive. My conclusion from experiments is that wired SONOS devices shall all be wired to the same Orbi device. There is no difference in wired to router, or wired to satellite. A wired BOOST is predictable root node. In my network I limit to one BOOST connected to RBS850 satellite that serves outdoor. This guarantees the outdoor SONOS speakers to connect to the BOOST with priority. Resulting connections show all green in the network matrix. Sonos outdoor runs smooth and stable. Would still Like to add a second BOOST to a second satellite. But Happy with current state.
Nice rundown.... some interesting conclusions there that I wasn't aware of.
This is most significant:
PTWA wrote:
My conclusion from experiments is that wired SONOS devices shall all be wired to the same Orbi device.Have you changed the root node at all?
Look at this article about Sonos on another vendor's mesh system (and how they solved it)
Does anyone know if (and which version) Spanning Tree Protocol is operating/implemented on Orbi AX6000 systems?
A good article on that and Sonos:
https://en.community.sonos.com/troubleshooting-228999/sonos-and-the-spanning-tree-protocol-16973
SONOS ZonePlayers use 802.1D Spanning Tree (STP) for loop prevention between wired ZonePlayers and the wireless SonosNet Mesh Network. The Spanning Tree running on ZonePlayers is compliant with IEEE 802.1D and can inter-operate with other IEEE 802.1D and IEEE 802.1w compliant devices. Note: IEEE 802.1w is an updated version of the Spanning Tree protocol called Rapid Spanning Tree. The two types of STP protocols are compatible and 802.1w should revert to inter-operate with 802.1D devices (such as Sonos). Therefore, 802.1w Ethernet switches will work with Sonos ZonePlayers
- In case changing the root node refers to SONOS advconfig capability, I did not experiment with this.
Now I have to report that today the satellite with wired BOOST stopped working. The Orbi app showed a Network diagram with the satellite having a red dot instead of a green dot, and still a dotted line for wifi backhaul. Power off and on with BOOST wired did not resolve the issue. The satellite white light kept blinking. After removing the wired BOOST and power cycle the satellite, it was ok again. Adding the wired BOOST again resulted in the same dead state of the satellite. Router and other satellite continue unhindered.
Now I moved the BOOST, and wired it directly to the router. I have no longer any SONOS device wired to any satellite. Waiting for the result...
I may have to withdraw my earlier conclusion that it does not make a difference whether a BOOST is wired to a router, or to a satellite.
Given the current state, and my outdoor SONOS no longer shows green in the SONOS matrix, I may experiment with a second BOOST not wired but assigned root bridge via the advconfig capability.
Question is what happened to the satellite, ending up dead. It may stem from the satellite again switching from wifi to wired SONOS backhaul, but now even a slow path did not exist, since a second wired SONOS device was not in the network??? Just a (idiot?) guess... no clue how to debug this one.
PTWA wrote:
In case changing the root node refers to SONOS advconfig capability, I did not experiment with this.
Now I have to report that today the satellite with wired BOOST stopped working. The Orbi app showed a Network diagram with the satellite having a red dot instead of a green dot, and still a dotted line for wifi backhaul. Power off and on with BOOST wired did not resolve the issue. The satellite white light kept blinking. After removing the wired BOOST and power cycle the satellite, it was ok again. Adding the wired BOOST again resulted in the same dead state of the satellite. Router and other satellite continue unhindered.
Now I moved the BOOST, and wired it directly to the router. I have no longer any SONOS device wired to any satellite. Waiting for the result...
I may have to withdraw my earlier conclusion that it does not make a difference whether a BOOST is wired to a router, or to a satellite.
Given the current state, and my outdoor SONOS no longer shows green in the SONOS matrix, I may experiment with a second BOOST not wired but assigned root bridge via the advconfig capability.
Question is what happened to the satellite, ending up dead. It may stem from the satellite again switching from wifi to wired SONOS backhaul, but now even a slow path did not exist, since a second wired SONOS device was not in the network??? Just a (idiot?) guess... no clue how to debug this one.I read in one of the listed articles that the boost had to be connected directly to the RBR (not a satellite) to avoid this loopback condition.
- Has anyone figures this out?
It's absolutely crazy to me that the RBS thinks that a connected device is a wired backhaul to RBR.
I have the same issue and it's driving everyone in the house absolutely crazy. Is there a way to force the backhaul path in Orbi so it connects to a specific IP address back to a specific RBR or RBS.
I have the same issue that after time or any type of internet flapping or instability the RBS reconfigures itself to shift from wireless backhaul to Ethernet backhaul via a hard wired Sonos speaker.
Current setup
FiOS to RBR
RBR wired to RBS1 to Arc and Sub
RBR wireless to RBS 1 to Sonos One
RBR wireless to RBS 2 to Sonos One
I have about 20 Sonos speakers on Sonos net - Looking forward to any stable solution !
In the meantime I run S1 wireless and S2 SonosNet with two Boost devices that are both wired to RBR. All further Sonos speakers not hard wired. This setup runs smooth, however still it would be great to get rid of the long wire between RBR and Boost for Outdoor. - Interesting...
I've noticed that my
hard wired Sonos ARC to RBS
hard wired RBS to RBR never experienced this issue. It's only when an RBS is wireless backhaul to RBR that I connect a Sonos speaker hard wired to RBS is when this issue happens - I observe the same. To work around I hardwire Sonos devices only to RBR and do not hardwire Sonos devices to any RBS. As a result the wireless backhaul between RBR and RBS is stable.