Post Reply 
mConnect and BubbleUpnP do not discover MinimServer
12-03-2024, 21:39 (This post was last modified: 19-03-2024 00:49 by Pepsican.)
Post: #1
mConnect and BubbleUpnP do not discover MinimServer
Hi

My issue is as follows:
Neither BubbleUPnP, nor mConnect will discover MinimServer, or they will discover it very slowly. It can easily take up to 15 minutes to discover MinimServer (by then I will give up and use something else to play music). And sometimes it will then disappear again. Bubble seems to be a little faster than mConnect to discover MinimServer, if it manages to find it. MinimWatch is also slow in finding MinimServer, but is much more rapidd than the cvontrol points. It will find it in under 2 minutes typically.

My network
- Router/Modem from ISP (Arris TG2492S). This device only acts as a Gateway/Router and it does some port forwarding for my game console.
- TP-Link SG2008P smart PoE switch. It does DHCP and the advanced L2/L3 switching (QoS, VLAN, etc), for as far as there is any.
- 2 TP-Link APs for WiFi
- Synology DS214+ on DSM 7.1 with MinimServer 248 installed
- Control points: Android12 phone with BubbleUPnP (licensed) and Apple iPad with iOS 17.4 and mConnect Lite
- Windows 10 on all PCs and Laptops on the latest version.

What I have done so far
- Added a rule to the Synology firewall to leave any MinimServer traffic alone (as found here on the forum)
- Checked everywhere (modem, switch, NAS) that IGMP Snooping is off (it is)
- UPnP is turned off for security reasons
- Defined the subnet in ohnet.subnet
- No Firewalls are blocking MinimServer traffic

Question: what am I missing to make these two control points find minimserver faster?
Find all posts by this user
Quote this message in a reply
12-03-2024, 22:56 (This post was last modified: 12-03-2024 22:57 by simbun.)
Post: #2
RE: mConnect and BubbleUpnP do not discover MinimServer
(12-03-2024 21:39)Pepsican Wrote:  Question: what am I missing to make these two control points find minimserver faster?

Given the delay, it sounds like the SSDP discovery broadcast isn't getting to MinimServer - or MinimServer's reply isn't getting back to BubbleUPnP/mconnect.

Is it possible to temporarily disable the firewall on your NAS and then open BubbleUPnP? An alternative test would be to enable the UPnP Server within BubbleUPnP (Settings > Local and Cloud > UPnP/DLNA media server settings > Advertise on LAN) and attempt discovery with mconnect on the iPad.
If either of these work then it's likely that the firewall on your NAS is blocking the incoming SSDP broadcasts.
Find all posts by this user
Quote this message in a reply
13-03-2024, 11:11
Post: #3
RE: mConnect and BubbleUpnP do not discover MinimServer
In a conventional home network setup, the router handles multicast messages and multicast discovery using the IGMP protocol. A device wanting to send a multicast messages sends the message to the router and the router forwards it on to all other devices on the network.

If IGMP snooping is enabled, the router attempts to optimise this by tracking which other devices should receive the message and only sending the message to those devices. This needs very careful setup to make it works correctly (i.e., not excluding devices that should be included) and this is why most users should run with IGMP snooping disabled.

In your setup, I am not sure which device is performing this function of multicast forwarding. My guess is that it would need to be the TP-Link SG2008P. I suspect that either this device is not handling multicast forwarding correctly or possibly your wireless access points are not forwarding multicast messages correctly.

Has this setup ever worked correctly for MinimServer? If so, powering everything off and on again might help.
Find all posts by this user
Quote this message in a reply
14-03-2024, 21:12
Post: #4
RE: mConnect and BubbleUpnP do not discover MinimServer
(12-03-2024 22:56)simbun Wrote:  
(12-03-2024 21:39)Pepsican Wrote:  Question: what am I missing to make these two control points find minimserver faster?

Given the delay, it sounds like the SSDP discovery broadcast isn't getting to MinimServer - or MinimServer's reply isn't getting back to BubbleUPnP/mconnect.

Is it possible to temporarily disable the firewall on your NAS and then open BubbleUPnP? An alternative test would be to enable the UPnP Server within BubbleUPnP (Settings > Local and Cloud > UPnP/DLNA media server settings > Advertise on LAN) and attempt discovery with mconnect on the iPad.
If either of these work then it's likely that the firewall on your NAS is blocking the incoming SSDP broadcasts.

SSDP discovery is active/enabled on the NAS.
Turning off the firewall made no discernable difference.
MinimServer has been added to the firewal rules and any and all traffic for Minim can pass through, both incoming and outgoing.
Bubble seem to pick up MinimServer somewhat faster than mConnect. But Bubble runs on Android and mConnect on iPadOS.
mConnect will discover Bubble on my Android. It will do it faster then detect MinimServer.

What rule would I need to create on the Firewall to keep SSDP open?
Find all posts by this user
Quote this message in a reply
14-03-2024, 21:21
Post: #5
RE: mConnect and BubbleUpnP do not discover MinimServer
(13-03-2024 11:11)simoncn Wrote:  In a conventional home network setup, the router handles multicast messages and multicast discovery using the IGMP protocol. A device wanting to send a multicast messages sends the message to the router and the router forwards it on to all other devices on the network.

If IGMP snooping is enabled, the router attempts to optimise this by tracking which other devices should receive the message and only sending the message to those devices. This needs very careful setup to make it works correctly (i.e., not excluding devices that should be included) and this is why most users should run with IGMP snooping disabled.

In your setup, I am not sure which device is performing this function of multicast forwarding. My guess is that it would need to be the TP-Link SG2008P. I suspect that either this device is not handling multicast forwarding correctly or possibly your wireless access points are not forwarding multicast messages correctly.

Has this setup ever worked correctly for MinimServer? If so, powering everything off and on again might help.

IGMP is probably done by the switch indeed as part of L2 options. Also, the router/modem provided by my ISP does not have any options whatsoever for IGMP. I searched Synology for IGMP but nothing came up so it seems the NAS does not support IGMP. That leaves only the switch with exposed IGMP functionality.

Now, I am not sure whether IGMP is actually enabled on my network. TP-Link's documentation is very deep about IGMP Snooping but not about IGMP activation without snooping. So, question number one is: how do I check that IGMP is active on my network?
Second question, if it is not, how do I activate it?

I updated the network last week. As MinimServer is a vital app for me, I checked it immediately and there are problems. So, they are there from the start. Also, the entire network was rebooted multiple times during its configuration.

The two Access Points have the option to convert multicast to unicast. The option was on. I turned it off. Not clear what the option actually does.
Find all posts by this user
Quote this message in a reply
14-03-2024, 23:13
Post: #6
RE: mConnect and BubbleUpnP do not discover MinimServer
Can you set up a minimal test network as a process of elimination? For example, can you connect the NAS directly to the SG2008P to eliminate the Access Points?
Find all posts by this user
Quote this message in a reply
15-03-2024, 07:47
Post: #7
RE: mConnect and BubbleUpnP do not discover MinimServer
(14-03-2024 23:13)simoncn Wrote:  Can you set up a minimal test network as a process of elimination? For example, can you connect the NAS directly to the SG2008P to eliminate the Access Points?

That is already the case Smile

The two APs and the NAS are directly connected to the switch. The switch then connects to the modem. The APs only play a role because of the wifi through which the iPad and Android phone connect.
Find all posts by this user
Quote this message in a reply
15-03-2024, 09:38
Post: #8
RE: mConnect and BubbleUpnP do not discover MinimServer
(14-03-2024 21:12)Pepsican Wrote:  SSDP discovery is active/enabled on the NAS.
Turning off the firewall made no discernable difference.
MinimServer has been added to the firewal rules and any and all traffic for Minim can pass through, both incoming and outgoing.
Bubble seem to pick up MinimServer somewhat faster than mConnect. But Bubble runs on Android and mConnect on iPadOS.
mConnect will discover Bubble on my Android. It will do it faster then detect MinimServer.

What rule would I need to create on the Firewall to keep SSDP open?
If you've enabled SSDP discovery on the NAS then that should have opened the necessary incoming ports too (I believe).
With mconnect able to discover BubbleUPnP (I assume near instantly) the next thing I'd do is install MinimServer (or Serviio if it's easier) on the PC that's attached to the same switch as the AP and NAS. If this works then it must be something to do with the NAS.

I'm not sure you actually told us what you changed with your setup?
Find all posts by this user
Quote this message in a reply
15-03-2024, 18:50
Post: #9
RE: mConnect and BubbleUpnP do not discover MinimServer
If you haven't changed the NAS configuration since it was last working properly, I think it's more likely to be an issue with the TP-Link switch or access points.

Can you install a control point such as Linn Kinsky or Kazoo on a PC or laptop directly connected to the TP-Link switch? This would enable you to test a setup without a wireless connection to the control point.
Find all posts by this user
Quote this message in a reply
17-03-2024, 15:17
Post: #10
RE: mConnect and BubbleUpnP do not discover MinimServer
(15-03-2024 09:38)simbun Wrote:  I'm not sure you actually told us what you changed with your setup?

My network used to be build up around the Synology and Devolo Powerline. That never performed satisfactorily (frequent interruptions and signal drops on the line, which often resulted in halted play lists). I therefore recreated the network, but this time using ethernet Cat6a cable and Access Points. The Access Points are powered through PoE, hence why the switch came into play. That also meant I could resolve another issue: every time when I had to reboot the NAS, the network would potentially get into trouble because the NAS was the DHCP server on the network. The switch now takes that role.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)