Skip to main content

Hello, 

 

I dont see any reason why the other Topic was closed. Refering to 

I will not accept the fact that this is just closed to say “Just put it in same VLAN”. 

This is far more like a F*** O*** statement towards your customers. 

The previous models, were pretty fine working, untill the ERA has been released. 

How hard is it to listen also to your customers who wants to secure their enviroment and put things in different VLANS? 

 

If this is not being fixed in the coming months, our stores in the Netherlands (35+), will not be onboarded with SONOS setups. To be honest, I still want this to get to work, but if this will stay like this, there is no other choice to see other brands. This is not a threat or a warning, just the facts. 

 

Hope that someone from SONOS reads this actually. 

And for people asking why you would want to segregate your network please consider something like this: you could have a Trusted network for personal devices (phone/Macbook/etc) 

When you take your personal devices away from your home network, do you create a separate ‘trusted’ VLAN for them to connect to, or do they connect directly to an untrusted public network?

And for people asking why you would want to segregate your network please consider something like this: you could have a Trusted network for personal devices (phone/Macbook/etc) 

When you take your personal devices away from your home network, do you create a separate ‘trusted’ VLAN for them to connect to, or do they connect directly to an untrusted public network?


NOT AT ALL…. 
with unlimited data, “always on VPN” connected back home…. 

Another finding, while I was doing some other troubleshooting… 

SAME network, but a DIFFERENT SSID… AIRPLAY will not work?!!! 

So just let check the facts here… it is the SAME /24 network… same GW… but a DIFFERENT SSID working on the same Network… it still isn't possible to STREAM over AIRPLAY?? 

So it looks to be more than only a VLAN/NETWORK seperation, there is also a bonding on the SSID which is being used on the client and the SONOS speakers???

As far as I’m aware, both the Sonos, as well as the device sending data to them, are still required to be on the same subnet. The stack that Sonos uses for access requires this. 

Terms & ConditionsCookie settings