Anyone who reads this and is curious about the result of the ticket,

OP set up ACL and it blocks the mDNS. That's the reason. It has nothing to do with the mDNS feature itself.

Hi @Markus123 

Markus123 wrote

  @Clive_A Thanks for your support once again! And for forwarding the request for the possibility to add more than 32 characters as Bonjour Service.

 

Because of Sonos, I checked again. And it does not work with the Windows Application. Here are all the settings:

 

WLAN "Omada Main" VLAN 20

WLAN "Omada Admin" VLAN 11

 

 

Network "Admin WLAN" VLAN 11

 

 

Network "Main" VLAN 20

 

 

My Sonos devices are in Network "Omada Main" and therefore in Network "Main".

 

 

 

No ACL's whatsoever:

 

 

 

 

Here the Bonjour Service for Sonos:

 

 

Here the mDNS AP settings:

 

 

 

If Laptop is connected to WLAN "Omada Admin" and therefore in Network "Admin WLAN" the Windows Sonos App does not find the Sonos system:

 

 

If Laptop is connected to WLAN "Omada Main" and therefore in Network "Main" (same as the Sonos devices) the Windows Sonos App finds the Sonos system without any problem:

 

 

 

=> Apparently something is missing... 

 

Important to know: The Android cellphones indeed do work! If Android cellphone is connected to "Omada Admin" WLAN it does find the Sonos system on "Main" Network. So apparently the Windows app is using different discovery than the Android cellphone. My problem: Actually I mostly use Sonos through a Smart Home Hub called "Homey". And this Smart Home Hub also cannot find Sonos if connected to different VLANs. So probably it uses the same discovery technique than the Windows App.

 

=> So if you could please ask your engineers if they could determine this discovery process? I wiresharked myself and could not find anything of use.. Thank you very much in advance!

 

Edit: If Android phone is connected to different VLAN it does find the Sonos system, but reproducable only after more or less 5 seconds. If on the same VLAN it takes maybe 1 second. So maybe the initial attempt of discovering the Sonos system on the android app is the same that fails for the Windows App and the Smart Home Hub "Homey" but does have a fallback discovery that seems to work. So actually it would fall through the wife approval if she has to wait 5 instead of 1 seconds. So I hope there's a better way that also works with windows and "Homey" and makes the discovery with a normal speed for android.

 

If the Android works, so it means the mDNS is working. So you are capable of the Wireshark and you may try to do this and test your Android.

It takes a second to see because it is broadcast not only in this VLAN but all. Expected.

At least I can tell you that mDNS should work and it is not a problem with the mDNS.

And next to the question about the discovery process. This is beyond our job because if you Wireshark and you find nothing about the Sonos and its mDNS, it means it is not an mDNS-based service.

So, use the Process Hacker and check the software port. It mainly uses 6969 and 64039 for discovery or related services. At least, that's what I find.

Update:

Turn on IGMP in LAN settings. Both VLAN interfaces.

In addition, you can try it. But I don't think it might help in SSDP in LAN.