Question

Will Sonos S2 support RSTP or newer STP path costs?


Badge

One of the consistent issues I (and many network implementors) have with Sonos equipment is dealing with the older/pre-standard STP path costs Sonos equipment presently uses (10 for Fast Ethernet vs the  commonly used 19). This is especially problematic with when multiple tiered switches are installed on a network and path cost modification isn’t practical.

Unifi (Ubiquiti) based switching networks can be especially problematic in this regard. Unifi switching can be set to STP or RSTP, but path costing can’t be edited persistently.

With Sonos S2 coming, are there any plans to modernize / update the spanning tree implementation to support the current STP path cost standards, or better yet, support RSTP?


12 replies

Since they haven’t yet released any specific information about S2, we don’t know yet. And if it is coming, but just not in the initial release, Sonos won’t tell us anyway, as they don’t announce software update features before they are released. 

Userlevel 1
Badge

Sonos, please support RSTP, or at least update your STP path costs! This is such a nightmare to deal with on managed switches!

Userlevel 1
Badge

I guess not… :(

Badge

Sad, this feels like such a missed opportunity to modernise the path costs.

As far as I’m aware, Sonos hasn’t abandoned their code base, and continues to develop it. There’s no guaranty that they’re not going to do this at a future time, only that they didn’t do it at this precise moment in time. 

very disappointing to see that S2 is still using the same antiquated STP implementation :confused:

I am a HEAVY user of Sonos right now.  We are looking at a new home build.  I work in IT.  I am considering abandoning Sonos over this issue.  It is pitiful this hasn’t been addressed.  It’s been a chronic problem for years.  It’s a simple fix.  It would vastly improve larger implementation setup with multi-tiered switches and larger Wi-Fi deployments.  And STP?  Support RSTP and be done with it.  Alternatively, let me disable the BRIDGE portion of WI-FI so I don’t get port blocking in the UniFi gear.  

 

I rarely comment in the forums here, but this is a pretty simple change to embrace a networking standard - of which your products really HEAVILY to make things work.  By supporting these standards, users will get more consistent results without as much frustration.  This is a win/win for everyone involved, not the least of which is SONOS own tech support team.  

Out of genuine curiosity, what does 'disable the Bridge portion of WiFi' mean?

And how is this affected by the fact that Sonos will often use direct routing rather than the STP paths anyway?

I am a HEAVY user of Sonos right now.  We are looking at a new home build.  I work in IT.  I am considering abandoning Sonos over this issue.  It is pitiful this hasn’t been addressed.  It’s been a chronic problem for years.  It’s a simple fix.  It would vastly improve larger implementation setup with multi-tiered switches and larger Wi-Fi deployments.  And STP?  Support RSTP and be done with it.  Alternatively, let me disable the BRIDGE portion of WI-FI so I don’t get port blocking in the UniFi gear.  

 

Sonos STP Switch Settings

Yes, you can implement the older STP which also disables RSTP.  This begs the question of why.  It’s because SONOS uses non-standard link costs in their RSTP implementation.  Anytime there is a new device added to the network, you’re going to have to wait 45 seconds or more just to get an IP address.  That’s stupid.  Update the route costs so RSTP works.  Bingo, bango, everyone’s happy.  

I think the rest of us are happy already. 

Pleeeeease do this. More devices use rstp now than stp. It makes sonos a nightmare in larger IOT home networks

Reply