mConnect and BubbleUpnP do not discover MinimServer

[Pepsican]

(18-03-2024 13:21)simoncn Wrote:  

(18-03-2024 11:54)Pepsican Wrote:  Is there a way to increase the frequency of NOTIFY? It could be a workaround? Is there a way we can check this? With Wirehark for example?

This is not possible with ohNet. The ohNet developers think the network should not be "flooded" with messages in an attempt to compensate (but only partially) for a basic fault in how the network implements the UPnP protocol. I think this is a reasonable position for them to take.

Yes, it is possible to check this with Wireshark. If you can capture all messages to and from the control point and to and from MinimServer when you start the control point, I will look at the capture file or files and tell you what is happening. I would need about 60 seconds of messages.

See the attached file. Here is what I did.
- restart the PC and kill as much traffic going to the NAS as possible (think Synology Drive, Windows File Explorer and its network shares, etc)
- start WireShark with filter "ip.addr=192.168.22.16"
- start Kazoo
- capture for some minutes. I could see NOTIFY messages

Initially not much was happening so I poked the bear a bit by telling Kazoo to "Rescan Network" under Settings. That sparked a flurry of activity.

I do see some odd IP addresses appearing that are not my subnet. No idea where for example 224.0.0.251 or 239.255.255.250 point to.

Edit: to be clear - 192.168.22.43 is the PC and 192.168.22.16 is the NAS. The subnet is 192.168.22.0.

Edit 2: Those strange IP numbers are IANA reserved IPs for Multicast. Any IP between 224 and 239 is reserved for that purpose. Just for those who don't know, like me.