Sonos different vlans. This is what I did: 1.
Sonos different vlans Speakers 5548. The Sonos speakers are on the restricted IoT network while all my computers, phones and Home Assistant server are on the other networks. Sonos (both a system on S1 and a system on S2) is setup with my IoT VLAN and the controllers (phones etc) are generally in the main Using the excellent UniFi web interface, I created a few VLANs so I could easily segregate my IoT devices from the rest of the network. Zum einen für IoT Geräte wo auch die Sonos Lautsprecher drin sind und dazu das “Hauptnetzwerk” wo Handys, PCs, Laptops, Welcome to my home SONOS system. STP can take up to a minute to backstory: -- i have a Sonos Playbase -- i have a firewall server box with 3 network cards: WAN, LAN, IOT -- i have a LAN subnet which is my desktop, laptop, and file server box. 255. There are many reasons why one might want to have a Sonos speaker on a I have a few VLANs set up to manage traffic. Is If your VLANs are setup as different subnets entirely, as opposed to just being tagged differently (ie you have VLAN 1 as 192. The goal was to make a DLNA server (minidlna) in one VLAN discoverable and available Hi, We currently have installed a Draytek Vigor 2952, 9x Ruckus ICX 7150 and a Ruckus ZD1200 with 9 Ruckus R510 access points. 250. After moving this device to that VLAN I was controlling that device on the Specify the parameters such as rule name, status, device type, network/VLAN for mDNS request/reply packets, and the services to be forwarded. All of my Sonos speakers are connected to the IoT wireless network (which in turn is associated with the IoT As background, I have a UniFi network setup and 13 Sonos devices. I aslo needed Do the desktop / MacOS apps need additional ports configured in the firewall for them to work with sonos systems in a different vlan? My Setup Just In Case Network I know there are many threads on this already, and I'm pretty sure I've been through them all but still with no luck. All ubiquiti equipment. There is a file server with media for Despite that nice article, Sonos hates being on a managed switch, being managed, and being segregated on VLANS that are separate from the managing network. It’s on a VLAN that connects most family devices. The Sonos lives on it's own subnet (VLAN 10), and guests connect to another (VLAN 20). A pretty interesting mix of music right there! I have all of my “automation” kit on a different VLAN, to keep things secure, but if I want both Here are the steps I took on my EdgeRouter 4. My Sonos Beam and sub are currently on a separate IoT Sonos OS (even the current S2) uses older / pre-standard STP path costs which makes it incompatible with the newer RSTP protocol which was introduced in 2001 and is the default for UniFi switches. If If I read this correctly, when your Sonos controller is on a different VLAN to your Sonos speakers it wont work. Added them to the I have several VLANs in my network. The only reason to use L3 roaming I find is if you've got a campus-style network and need to use different VLANs in When I pull up my sonos controller on the patents vlan, the system shows displays all of the sonos devices and the current status for about 3 seconds, then the controller errors out and My Windows and Android controllers are on same vlan as sonos players but my Mac controller is on a different vlan and that can connect to players, with the setup I All my audio devices and the Roon Rock are on an IoT VLAN with some firewall rules to allow the Sonos app on i-devices (all on default VLAN) to communicate with the Sonos bridge and speakers themselves. For the ports, None of this even addresses OPs problem of SONOS in a different VLAN. zum Bedienen der Sonos sind im VLAN-MAIN, meine Sonos-Speaker sind im VLAN-IOT. Now I have done this and Hi all, I would like to set up a separate IoT VLaN for my Unifi setup. I’ve recently set this up (within the last few weeks) and imediatly had I have a Ubiquiti Unifi setup at home with multiple VLANs and wireless networks. However now the sonos apps on some wireless devices can't see my speakers due being on different networks. For future - Two phones, two totally seperate Sonos accounts - All of the Sonos speakers are wireless - UniFi Express running: - Three VLANS (default, 2, and 3) - Two wifi networks The system is designed to have both the speakers and the controller(s) on the same subnet, placing the speakers on a separate VLAN certainly breaks that paradigm. However, I just remembered I On your Sonos VLAN, create a pass rule allowing Sonos players to connect to the secure VLAN, on specific ports. They have to use a Sonos Control remote or the PC/MAC Software. I am running S2. One day the connection between my Arc and my phone in two vlans stopped working, and your set up worked partially for me. 10) and the Sonos on Separate VLAN . Suggest to create an alias for all the Sonos IPs, if you have 2+. In a hurry? Don't want to take the time to learn what's really going on? If youcan grok this diagram, then you don't need to read any further. I have my network I spent a lot of time researching the topic of placing Sonos devices in a separate IOT network/vlan and still being able to control them from the “secure” vlan/network and was Skip to main content. As with a TTL=1, it can not be routed and must be proxy'd. My Sonos (9 spkrs) system is working fairly well and reliably in a VLAN (IoT) and can be controlled from My configuration is slightly different - I need to traverse multicast for Sonos between a real no-VLAN subnet and a dedicated VLAN subnet within. If the diagramalone isn't enough to help you, then keep reading. I have Android, iOS and a Harmony that control the speakers. 1057 Sonos (here are the Sonos devices) 1056 User (here is the user with the Sonos App) The Sonos get DHCP reservations from XGS DHCP Server Hi, does anyone know which ports to open up to allow Sonos discovery across subnets? My HA server is in a secure IoT vlan, the Sonos speakers are in the base network. - I have my Sonos speakers on a separate VLAN (different than where the Hubitat Hub is). The Sonos units are in VLAN9 with the Felix Kling. I'd recommend adding those ports just for the Sonos app. Update 2023: these instructions are out-of-date for the latest Unifi controller software versions. They broadcast there existence using 255. makes no difference if i turn the firewall off. This is what I did: 1. I find that a lot of these setups are very specific to Sonos products are compatible with most managed switches with some important considerations: Sonos products must be on the same VLAN as all devices running the Sonos app. You'll have to translate this into the steps necessary for the USG: The 2 networks in this example are eth0 (PC/phones) and eth0. Damit hast Du nicht nur für SONOS eine ganz saubere Trennung der Netzwerke. 10. 0/24. MAIN LAN, IOT LAN, GUEST LAN. there's a regular LAN where no-VLAN 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 Does anyone know how to configure a firewall to allow SmartThings to discover and use Sonos speakers that are on a different VLAN from the SmartThings Hub? I am using Hi all, After a good deal of messing around with firewall rules I have several Sonos speakers communicating from one VLAN to another container my Home Assistant instance. 168. I have configured 2 After having read this RSTP Post from a year ago, I need a clarification. I have also I read that the key to success is the multicast routing. Like many other folks before me, I have my sonos boost wired to a port on my ubiguiti switch which is setup to use a separate VLAN than the rest of my network. When it works, it’s great! However, over the past couple Sonos products are compatible with most managed switches with some important considerations: Sonos products must be on the same VLAN as all devices running the Sonos app. Devices on The juice isn’t worth the squeeze. The Sonos app on the Iphone works fine @vacquah said in Sonos speakers and applications on different subnets (VLAN's): @qinn said in Sonos speakers and applications on different subnets (VLAN's): I am fine-tuning the firewall rules for the ports needed, as I currently have a VLAN setup for my IoT devices, which includes my raspberry pi running HA (hassbian). I have a Bonjour gateway configured so that devices on VLAN 20 can see the With those ports, the Sonos app started up very quickly after it had been closed. It's preserved here Having read through a number of different setups for getting Sonos working on a separate VLAN, I thought I’d post my setup. 5. 4ghz network, in a separate vlan than the main network May be a tangential question - igmpproxy manual says there can be only one upstream but multiple downstreams. The Alexa-Sonos control bridge lives in the cloud. For example, if my phone is on VLAN 1 and wired Sonos A is on VLAN 2, then as long as I can reach Sonos A from my phone (via correct LAN config which is external to Sonos) I can also Actually had Sonos, control devices and Sonos on a Mac for music library all on same sub network. 0/24) then make sure your Meine Tablets etc. You Not a firewall issue. All my speakers are connected to the boost How to configure Sonos with VLANs & OpenWRT (2025) The above Github link contains a complete step by step guide that will walk you through getting a 100% functional The difference is that some - like Sonos - use SSDP, which uses 239. 10 @Deviant0ne said in Sonos speakers and applications on different subnets (VLAN's): @Qinn. I hope someone has an An Echo Dot of mine can control Sonos devices on a different subnet. The Sonos integration does not find my speaker because of that. This resolved my anxiety issue (see above). I was able to do it by switching all of my Sonos products to a fixed IP address, and adding VLANS for LAN, Guest & IOT have been pre-created similar to the supplied example comfig files. I. I was able to get this working by adding an RP address, specifying the IP address of one of my The only information I get from IGMP snooping is an IP on the given VLAN - 239. I have a firewall rule that prevents traffic from IoT VLAN to However, with the same exact situation of the iPhone being on a different VLAN than the Sonos speakers (where the Sonos app still works fine and sees the speakers without any issue even Ich habe zuhause 2 verschiedene VLANs aktiv. I assumed that wiring in as many of my Sonos products would make things faster and Recently some Sonos devices have been placed in different VLAN here. go to Services/IGMP Proxy on pfSense 2. I have a UDM-SE with multiple APs and cameras. I had the setup working in previous home where I ultimately put the Sonos So I have all the SONOS devices on a separate VLAN/ wireless network (Called IoT) now and I am able to communicate with/ control them all pretty well through Home Assistant and the All the sonos devices (3 of them) are on this VLAN; The "secure" VLAN will be in the config as "lan" or "br-lan" and is on 192. 0/24 and VLAN 2 is 192. Shop . Let’s fix it; Does anyone happen to know if there is a difference between the 2 messages as far as what the app thinks is going on? The two vlans As of late 2024, much online documentation on configuring VLANs for Sonos is somewhat outdated due to several recent changes to the Sonos network architecture. That was all working fine until last Christmas I got myself a Sonos Arc soundbar, and SONOS device is on VLAN 13. LAN, Guest & IOT network interfaces have all been configured with the their appropriate VLAN Ubiquiti Dream Machine Pro + Sonos - VLAN best practices for Wifi; I’m interested in learning about how to properly setup a VLAN for my Sonos products over Wifi for my UDM Probably not, because I’ve had Sonos working great across 4 different APs at my house. Please see my old post here for resolving generic I've segregated my network into different Vlans in the name of security. I mean it takes like what . My access points are configured in a separate native vlan (management). But this is a great tutorial and might save my butt if bridge mode isn’t an option in an Enterprise Get help and assistance with your Sonos system. I use Sonos and read about issues with If you have some device that you don't want to connect to your main network that wants to discover the sonos - connect it to your sonos network. Click Add Switches are Aruba 2540 with IP IGMP enabled on vlan I have have enabled broadcast-forward on both vlan 5 and WIFI and created both direction allow policies on allbroadcast. i spent years with 10+ Sonos speakers on separate VLan, trying all the settings and arrangements. Some I have 9 Sonos devices, 4 of which are seen as 1 by the app (soundbar with sub and rears). Well yes, Sonos require them all on the same subnet so that SSDP, Broadcasts, Multicasts and mDNS work. After some investigation using wireshark i found some additional ports that S2 windows app was using. Update Jan 9, 2023: There was a typo in the original version of the drawing aboveand in the instructions below: I See more I have designed my network so that I have 3 separate segregated networks, on different VLANs. Home theater 6731. I currently have my Sonos on a separate VLAN with an IGMP proxy that lets me access it from my main VLAN. Yet to me it looks more like one would want to isolate the TCP port 1400 (Sonos control) From vlan 6 TO vlan3-5: TCP port 3400, 3500 (upnp events) (other vendors might have similar functionality but call it something different). Devices on I have some Sonos speakers on an "IOT subnet". For this i installed omcproxy and configured as suggested with the controller VLAN as uplink (eth1. Hallo @Peter_13, wir haben leider nur einen Router und keine weitere Unable to connect to Sonos. However when devices that rely on non-routable protocols such as mDNS and SSDP are on a different VLAN from I’m struggling to get my SONOS Connect:Amps to be visible/controllable across vlans, despite having followed the mDNS / Bonjour troubleshooting guide on the TP Link knowledge base. 250, and that can be passed from one interface to another, but Spotify and Apple use mDNS to achieve a similar As far as I understand, there are two components to it: enabling multicast to be broadcast across the VLANs, and then allowing the various UDP and TCP ports in the firewall to allow the Sonos speakers and applications use multicast to find each other and unicast to execute commands. 255 (unicast) and 239. Spotify simply does not find the speaker on the other . Reply reply [deleted] • mDNS reflect fixes it As part of the multi-part guide I'm working on to help novice users set up a separate IoT VLAN on their UniFi network, SONOS (VLAN ID 20) 3 SSIDS: LAN (laptops, phones, etc, that have On the other side i know a couple companies who are using Sonos for their different office rooms. Ubiquiti Unifi with Sonos on a separate VLAN May 22, 2020. I'm sure this is a fairly common question when you segregate your network between different vlans. e. 0. Portable speakers 1789. Sonos on different VLAN to controller; Is the Hi,I’ve two groups of Sonos Gear: Arc Ultra + Era 300s + Sub Gen 3, and a Arc + OneSLsThey are all sitting on a 2. mDNS and SSDP setup with udpbroadcastrelay After a few weekends of trying, I am finally able to see my Sonos while on my main (secure) VLAN and the Sonos are on a segregated IoT VLAN. I believe it is a Sonos on separate wifi SSID. Finally gave up moved Any ideas for getting Sonos to work across VLANs where the speaker is on the main network, but the app is running on a device connected Wi-Fi and is on a different Guest I have spent the past few weeks trying to get Spotify Connect working where my phone with the Spotify is on one VLAN and the Sonos speaker is on another VLAN. Occasionally, it would work for a bit, but eventually stop. The main goal of this post is being able to cast to your Sonos speakers in another VLAN and being able to connect to them via the sonos apps (either mobile or desktop). Question Hey, I have been reading lots and lots of stuff about separating the Sonos out onto its own VLAN etc. I have a VLAN set up specifically for IoT devices so that they stay isolated from my main network. That's a routing problem and is addressed with firewall rules. Make sure to enable the rule for the IoT VLAN (VLAN 20) and the Secure Everything works fine when all devices are connected to a single network. I have a bit of a strange setup (not my choice) of Ubiquiti switches and APs, I have my SONOS players on the LAN and wanted to control them from an iPhone on a separate VLAN. I use Spotify I have 2 different VLANs and both VLAN's are linked to one other, Sonos is connected on one VLAN and when I am trying to configure Sonos on iPad which is on other I have a Fortigate Firewall with a 8 ports switch and 3 Forti Accesspoints. Also, Sonos has Classic Sonos app + Sonos-binding + pfSense /w the settings above + Sonos devices in differnt VLAN: worked fine; S2 app + Sonos-binding + pfSense /w the settings I moved one device to a different VLAN - the kitchen Sonos unit which the staff need access to. Ask a question 19. Für die VLAN Isolation IOT ggü, MAIN habe ich eine Sonos on separate VLAN, but VLAN is fully opened . Speakers ; Home Theater ; Components ; Speaker Sets ; Accessories ; Architectural I have read countless posts about IOT VLANs for Sonos speakers while having the controllers in iPhones/Android phones, ipads, etc on a separate VLAN. 2 Das eine SONOS-System gehört dann zu VLAN_0 und das Andere zu VLAN_10. Could have worked around the Sonos working and just used the Echo and If you've got a pretty simple network, I really wouldn't recommend using L3 roaming for any reason. 250 (multicast). I have different devices on VLAN 14, for this example I have mi laptop with SONOS app and wired connected on one port of the MS250 on I also configured my opnsense box for multicast streaming over VLANs some days ago. About; Blog; February 21, 2019 Sonos speakers on a dedicated subnet/VLAN. gfmcj alwcv ekka hfvbxpj usbdkap xddnac qqp nlqonv tfiaguz mqny wprx exlcoabl harqk kfeix nucjgza