Hey @Florent ,
I fired up Wireshark and did some packet sniffing this afternoon, I was connected wirelessly to the SSID tagged to VLAN 201, VLAN 201 is where my clients and most of the media devices reside, either wired or wirelessly.
I can see mDNS requests for Spotify Connect and replies from some of my Sonos players (via the Aruba AP Airgroup / Shared Services service), it’s a mixed bag of my Sonos players on who replies: some old players, some new players, some on wired on ethernet, some on Sonosnet wireless (these on Sonosnet would appear as wired devices to the Aruba AP)., that would actually mean that all my Sonos would appear as wired clients as they are in WM=0 mode (sonosnet) as I can't get them to work on the Aruba wifi as clients in WM=1 mode.
I can see SSDP requests from clients and replies from my Sonos players (via the Aruba AP) as well but I believe that Sonos also uses other broadcast traffic for speaker setup, etc. I will try and sniff this traffic at a later date.
When I open the Sonos app on my MBP, I can see in Wireshark that it does a SSDP search to:
239.255.255.250:1900 (multicast)
255.255.255.255:1900 (broadcast)
Looking for:
urn:schemas-upnp-org:device:ZonePlayer:1
And then Aruba AP returns a pile of responses with all the Sonos players on the network that have that Service ID. So that one part appears to work. I can’t tell whether AP is also communicating the other DLNA/SSDP Service ID’s that Sonos uses.
I haven’t seen any _sonos._tcp requests or replies being made on the wireless, so I don’t know how those fit in. Haven’t had chance to contact Sonos support yet to see if they can provide any insight.
I did however see the AP query for a long list of mDNS services, and those did include:
_sonos._tcp
_spotify-connect._tcp
_hap._tcp
_homekit._tcp
_lutron._tcp
etc.
I’m also having issues with SSDP and the DIAL protocol. I have two Nvidia Shield 2019 on my network, one is connected via ethernet, one is connected via wifi, both on the same VLAN.
When I go to cast on my Android Pixel 3a phone in apps that use DIAL (Netflix):
-Shield on wifi —> not visible
-Shield on ethernet — > visible
Same in Chrome on MacOS which also uses DIAL. The mDNS (googlecast) on both Shields seem to work okay.
So I also fired up Wireshark on the wired side of VLAN 201, my Windows 10 PC, and saw something interesting, the Aruba Airgroup / Shared Services service does NOT send out queries for mDNS or DLNA/SSDP services down the wire, it appears it just listens to what is on the wire. When I opened up my Spotify on the wired side of VLAN201, then all my Sonos speakers, which reside on wired side, appeared on the wireless side of VLAN201 as all the Sonos speakers send out a mDNS response for the Spotify Connect mDNS request and the AP picked that up and must have put in it’s cache. There are strange things happening with Airgroup/Shared Services with VLAN’s as the AP isn’t keeping services confined to their respective VLAN even when the service isn’t checked to be shared. I have a ticket open for this already.
I had mentioned earlier that my MBP couldn’t see all my Sonos airplay targets, it appears that the MBP isn’t doing mDNS requests for airplay targets so that’s possibly an Apple issue? I do the see the Aruba AP querying for airplay services but only on the wireless side and I have clients on the wired side but they never see the request from the wireless clients. I don’t know if maybe the MBP is expecting unsolicited advertisements of the Airplay servers as well? Again, these don’t appear to be making it through from the wired side for some reason.
I’m like to spend more time on this but I’ll have to save it for another day.
-Scott.