Sonos speakers and applications on different subnets (VLAN's)
-
@johnpoz said in Sonos speakers and applications on different subnets (VLAN's):
I am just surprised to be honest the amount of interest in what I would think is a niche thing.. Most users that have the $ to get sonos normally have a guy ;) hehehe
My nephew has some sonos, and when I ask him if he wants to chat or needs any help in setting up anything.. And we have discussed stuff.. he has "a guy" that his company uses, that comes over to the house and shows him what button to press ;) hehehe
You're probably correct to some extent. I am sure that there are a lot of people with money who buy these systems and hire "a guy". But, there is also a more hands-on enthusiasts group like myself. It's like people who buy a BMW or Mercedes, some do it just because they have the money, others because they are really into cars.
-
True... I would have sonos myself - but would not be able to get it past the budget committee (wife) hehehe
Not really because I need them... But I would like to play with the tech.. House isn't big enough to justify them for another.. When turn on sound system you can hear it across the street, so no need for speakers in other rooms of the house ;) And if want to listen to music out of the patio or something just grab my portal bluetooth bose..
-
@johnpoz said in Sonos speakers and applications on different subnets (VLAN's):
What I mean by wifi X, is the ssid and L2 that your sonos is on... For example if I need to discover a new roku or something I connect to that wifi network.. Discover it, and then once discovered I can move back to the normal wifi network.
If I need to do something with network X's at an L2 level - then I join that network... Ie I push this button, then that button ;)
I am certainly no expert on Sonos's system but I don't think that you can directly access their proprietary network. It doesn't work that way.
-
Doesn't matter - not talking about whatever their network they create.. Talking about the L2 you put their speakers on be it wired or wireless.. If you want to discover the hub or master, then you join that network..
The only time this becomes an issues is when you create new networks.. And your device is on network X, and the speakers on network Y... So when you want/need to talk to the speakers then just connect your device to network Y.. Bridging networks via multicast routing is not a good thing... How freaking hard is it to click join network Y on your phone or tablet... Since you clearly have created multiple networks or you would not have this issue in the first place.
Ie press button X, then button Y.
-
@johnpoz said in Sonos speakers and applications on different subnets (VLAN's):
Doesn't matter - not talking about whatever their network they create.. Talking about the L2 you put their speakers on be it wired or wireless.. If you want to discover the hub or master, then you join that network..
I'm afraid you're talking way over my head. I have only the most elementary understanding of L2 layer networking. Fortunately, my current setup is working perfectly, learned a bunch in the process and all is good!
-
So are you using igmp proxy or the new pimd package? Or do you have just 1 flat network.. Do you have multiple vlans, multiple ssids that are different networks?
Sonos is meant to be on the same network your phone and tablet you use to control them join.
-
@johnpoz said in Sonos speakers and applications on different subnets (VLAN's):
So are you using igmp proxy or the new pimd package? Or do you have just 1 flat network.. Do you have multiple vlans, multiple ssids that are different networks?
I am using the new pimd package. Igmp proxy doesn't work, it apparently has been broken for quite some time. This all started because I wanted to put my wifi AP on it's own subnet. When I did this, I couldn't access my sonos devices from my iphone. I am not using VLANs but physical interfaces.
-
@johnpoz said in Sonos speakers and applications on different subnets (VLAN's):
Sonos is meant to be on the same network your phone and tablet you use to control them join.
yes, i know that's is how it is designed, but, you know how we are, always looking for a work-around
-
@johnpoz I do agree with what you're saying!
I joined my Sonos VLAN (created a temporary SSID on with the same VLAN tag) and discovered the Sonos bridge. This was a one off activity and I can now discover the Sons speakers without the need to be on the same Sonos network, although there is a quirk with their iOS app which requires the wifi to be toggled off and on for it it work. The macOS has no issues discovering the Sonos system after the initial discovery.
-
@johnpoz said in Sonos speakers and applications on different subnets (VLAN's):
Your dropping 1k$ on a couple of speakers, how about get a real freaking switch is all I am saying ;)
Actually - nope ;) Thanks to the IKEA coop, you can pick up Symfonisk Speakers (with about the same tech as a Sonos One) for as less as 99$/179$ (if you take the shelf or lamp speaker).
Also I'm running very capable switches, but do I want to set up the networks on my switch (with bad filtering if at all) or do I want them on my actual firewall that can do filtering oh so much better? Sure thing :)But as this whole pimd setup isn't working (was only a test anyway) for me at least, I'm happily stay as it is with all the "cast"ing hardware like Chromecasts and Sonos in the streaming VLAN and just control them via my WiFi Setup (Radius-based VLANs and an additional classic WPA2 one for the streaming thingies as some of them don't speak "enterprise" WiFi). Works well enough. But with pimd working there had been a chance for wife's and kid's phones to just stay in their WiFi VLAN but able to stream/control the cast boxes from there without having to add them to the casting VLAN. Makes outbound NAT and filter rules easier if you can set up the whole VLAN instead of having to group IPs together, do Alias groups yada yada yada. Also as ISPs IPv6 is pretty fucked up, I'm using a big /48 tunnel from he.net but the Casting VLAN has IPv6 disabled or no streaming TV for us (Prime and Netflix are complaining about being in US rather then EU blahblah Geofencing). That's why I put those phones and other trusted WiFi stuff in it's own VLAN with IPv6 enabled.
Yeah you could set that up, too, but it's a mess and having it separated and clean is really fun. But so be it, switching WiFi to control it is :)True... I would have sonos myself - but would not be able to get it past the budget committee (wife) hehehe
Just have a look at those :)
https://www.ikea.com/us/en/news/symfonisk-wifi-speakers-pubaafe6500I bought the small soundbar from Sonos as the new TV came and it wasn't that much more or less expensive than other solutions but as we also listen to radio, streaming, audible etc. it was quite appealing to buy the Beam at that time. Added two rear speakers with the IKEA ones (the shelf speakers) and they are great. Maybe lacking as a single/pair but as surround addition they are quite nice. Just added a lamp speaker in the daughters room as she needed a lamp anyway and loves listening to music and audiobooks while doing other stuff so the system pretty much grew by itself
-
@JeGr said in Sonos speakers and applications on different subnets (VLAN's):
but do I want to set up the networks on my switch
This is completely not understanding how multicast works...
An intelligent man is sometimes forced to be drunk to spend time with his fools
If you get confused: Listen to the Music Play
Please don't Chat/PM me for help, unless mod related
SG-4860 24.03 | Lab VMs 2.7.2, 24.03 -
Sonos utilizes the Simple Service Discovery Protocol (SSDP) to discover devices on the network. SSDP uses the site-local multicast address 239.255.255.250 and UDP/1900 for IPv4.
The Sonos controller software discovers the Sonos players by joining the multicast group 239.255.255.250, thus the network needs to support and forward multicast.
-
@johnpoz said in Sonos speakers and applications on different subnets (VLAN's):
@JeGr said in Sonos speakers and applications on different subnets (VLAN's):
but do I want to set up the networks on my switch
This is completely not understanding how multicast works...
Nah I get you. Just wanted to point out the reasoning why to seperate in the first place and why most people (in home environment) try minimizing the main point to configure things to only one instead of multiple (switches, etc.). But yeah, you could use the switches to forward multicasts, only it's often a WiFi (only) setup so potentially no switch involved :)
-
@edz said in Sonos speakers and applications on different subnets (VLAN's):
@jimp said in Sonos speakers and applications on different subnets (VLAN's):
Captive Portal would be my top suspect, followed by floating rules.
Hmm, I don't have Captive Portal enabled on pfSense, I'll check floating rules but I am seeing IGMP traffic coming in on my Sonos VLAN. I am receiving this error on 2 VLANs, one with hard wired Sonos speakers and the other on my WLAN VLAN. I'll check if Unifi is blocking any multicast traffic on WLAN, but I'm sure I turned this off previously as it caught me out when I setup Avahi.
The error you showed would be outgoing traffic blocked, not incoming. So you may see it enter that interface, but something is preventing pimd from transmitting. And the error suggests it's firewall-related, which means things like Captive Portal or floating rules. All traffic is allowed outbound by default so it must be something that's been configured on there.
-
Firewall rules you have made to pass multicast are UDP.. right?
-
@jimp said in Sonos speakers and applications on different subnets (VLAN's):
The error you showed would be outgoing traffic blocked, not incoming. So you may see it enter that interface, but something is preventing pimd from transmitting. And the error suggests it's firewall-related, which means things like Captive Portal or floating rules. All traffic is allowed outbound by default so it must be something that's been configured on there.
@chpalmer yes I am certain UDP was allowed on all interfaces.
Anyway...I took the brute force method - started from a fresh install and went back to 2.4.4. Followed the screenshots above and IT WORKED! Now running 2.4.5 RC and things are working great, thank you all :) -
As I had promised in an earlier post, I would like to share my experience using pimd pkg v0.0.2 configured with the same values as the manual installation. After spending hours selectively deleting and playing with these settings, I have come to a few modest conclusions. It should go without saying that your experience might not be the same due to your setup. My setup is relatively simple, I have my wired desktop clients, WiFi AP clients and Sonos devices each on separate interfaces and subnets. These are physical interfaces and not VLANs.
The "Tree Switch Threshold" settings which had been previously configured as "Threhold Type>Packets" and "SPT Interval>100" do not seem to be necessary. I went back to the default settings without any impact.
The BSR (Boot Strap Router) Candidates and RP (Rendezvous Point) Candidates settings, however, appear to both be critical. As a matter of fact, the Rendezvous Point address is actually listed in the status report under "RP Address" . A Rendezvous Point address does not appear to be selected without also setting the BSR Candidates values.
I did play around with changing the interface on these two settings. The description on both state "When set to "default", the feature is enabled without a specific interface, which will default to the highest available IP address." In my case, the highest interface address is the interface dedicated to my Sonos devices. I tried changing it to my LAN interface but it did not seem to make any difference. It still seemed to work. Although, it doesn't seem to impact my set-up I would be very interested in learning under what conditions one would chose one interface vs another. It might make a difference for someone else.
A question for @jimp . Should there be default settings for BSR Candidates and RP Candidates? There appears to be for the manual installation.
As all of this is completely new to me, I have made an attempt to educate myself as to exactly what these settings mean. Unfortunately, this stuff is way over may head and gets complicated quick . To quote @johnpoz "...routing multicast is pretty high level networking shit... " I would certainly agree. Maybe one of the fine members of this forum would be willing to offer us newbies a primer on this topic?
For those Sonos owners who are using Spotify, you no doubt have come to enjoy the ability to route your listening to a variety of devices including Sonos. Spotify calls this Spotify Connect. As a matter a fact, I generally access my Sonos devices when I am listening to Spotify via the Spotify app and not the Sonos controller app. What I have discovered is that (with my set up), Avahi is necessary for this to work across subnets. It does not work with pimd alone. Whether pimd is even needed I am a bit uncertain. I have not done extensive testing, but I have turned off pimd and Spotify Connect still discovers my Sonos system. My Sonos controller stops working but the Spotify App still works. I have tested this using the Spotify iOS app and both Linux and macOS desktop apps.
-
@wanabe said in Sonos speakers and applications on different subnets (VLAN's):
A question for @jimp . Should there be default settings for BSR Candidates and RP Candidates? There appears to be for the manual installation.
It's something we can consider. I didn't put anything in by default because originally the suggested configs earlier in this thread for pimd only mentioned enabling/disabling interfaces and nothing about BSR/RP/etc.
If I did make a change like that it would only affect brand new installs and not upgrades.
-
Thanks for all the good information here in this thread. Because of it I have a mostly working setup, however I don't know of anyone here can help me with the last pieces of my setup because I am using HEOS rather than SONOS. The Denon AVR app works across vlans but the HEOS app has a curious behavior. Each time I launch the app the first input that I provide the app gets executed but the UI doesn't update and it doesn't respond to further commands. I'd appreciate a little help on how to narrow down what configuration issue I may be having.
-
Hi @xeroiv , Sorry, I don't have a Heos Speaker to test this out for you, but suspect HEOS may have different ports that it is using?
Are you able to share your firewall rules on how you got the Denon AVR app to work across VLAN's?
@All - Thanks for sharing all your inputs thus far. However, I have only had limited success following inputs from this thread :
- Ability to manage my Sonos using the the Sonos Controller app on my LAN
- Unable to Airplay to Sonos devices from outside of the VLAN
- Lock screen controls on iOS don't work, but I suspect this is a Sonos App limitation, rather than anything to do with the firewall rules.
