One wonders how the core OS code Sonos is using supports that sort of thing. Been years since I looked at what little information is available on that topic.

Also Sonos isn’t going to spend a lot of effort on stuff that won’t sell significant numbers of speakers or that adds to the code size impacting what speakers can use the new releases.

I anticipate you are right but that doesn’t mean it’s a business savvy decision. Sonos is generally used in higher end environments and with that the likelihood of networks being ‘flat’ is much less than it used to be. And daily new advisories are available to separate IOT from computers that are used for work/administration/business/pleasure etc. Increasingly modern routers have consumer friendly settings to creating VLANS. 

Sonos should figure out how to keep the easy setup for those that need it but add an ability to specify IP addresses for devices in an advanced setup so that traffic can traverse networks. It's a lot less complicated than is portrayed by Sonos. We all stream audio / video in 4K over the internet (and in multicast style) without issue.  Even latency doesn’t have to be a problem….  

What is your use case for VLAN(s)? Are all Sonos devices on same VLAN, and you want to access/control from another VLAN?

VLAN support? LOL. The mobile app still has trouble reliably finding devices on a flat subnet, and you are complaining about segmented VLAN support.

I have customer subnets that are large enough to require to have devices across various VLANs.. But yes.. I would like to access SONOS locally regardless of what local VLAN it lives on.  

I know… what am I thinking… right? 

Move them to one of the bigger private address spaces, I use 172.16 here.

10.0.0.0        -   10.255.255.255  (16,777,216 addresses)172.16.0.0      -   172.31.255.255  ( 1,048,576 addresses)

Yeah… Feel free to try and make it work at scale. It’s a work around (not a solution) that would cause many other headaches and cripple other critical systems depending on a reliable and low latency network.. I’m a fanboy just like you (just don’t have over 11K responses here on this forum) but here are other IP based amplifiers that work. 

SONO stock down 66% from all-time high. I hope, I really do, they are able to turn this around. We just can’t wait for that. 

I don’t think VLAN support is anywhere on their radar. 

Too long retired to try it at scale.

VLANs are interesting and have uses but for larger networks you run into limitations based on the routing hardware’s MAC cache size. I don’t have access to high end gear anymore but I have 8 and 16 Kb caches here, and there is no way I’m going to get past a 200 hundred clients.

I can imagine how happy the Sonos Support folks would be to add supporting VLANS to their already tough set. My current ISP uses VLANs on their Smart NID (fiber to Ethernet converter) and the number of support calls that generates is amazing considering it is a “set once and forget” option, well until you buy a new router.

You can control the Sonos devices with the controllers on same VLAN, have separate VLAN(s) for other non Sonos devices? Why do you need to put controllers on a different VLAN?

Most (all?) consumer smart home devices don’t play nicely with enterprise networks, thinking out loud, Apple HomeKit/AirPlay, Google Home/Chromecast, Amazon Alexa, etc. If these products did support enterprise networks, consumers would have to pay enterprise prices.