Minimwatch doesn't connect to minimserver on qnap

[simoncn]

(25-04-2023 14:33)gotburger Wrote:  The operation: Move one of the QNAP interfaces to subnet 192.168.20.0/24
Now:
- The MinimServer does NOT show up in Linn Kazoo on the 192.168.50.0/24 subnet

When you set the MinimServer ohnet.subnet property to 192.168.50.0, the ohNet stack (used by MinimServer for UPnP communications) makes an arbitrary choice of a single adapter on the 192.168.50.0 subnet. If it has chosen the adapter that you later change from 192.168.50.0/24 to 192.168.20.0/24, control points using the 192.168.50.0/24 subnet will no longer be able to see MinimServer.

The solution is to remove the ohnet.subnet setting for MinimServer. This enables MinimServer to send UPnP advertisements on all available subnets. Alternatively, you can leave the ohnet.subnet setting as 192.168.50.0 and stop and restart MinimServer using QTS App Center after changing the adapter subnet to 192.168.20.0/24. This will cause MinimServer to select an adapter that is still on the 192.168.50.0 subnet.

Quote:- The MinimServer status page is accessible over BOTH 192.168.20.0/24 and 192.168.50.0/24

The MinimServer status page is accessed using HTTP, not UPnP. The ohnet.subnet property controls UPnP access to the server, not HTTP access.

Quote:Haven't found out whether 192.168.20.0/24 is served instead.

This should not happen if ohnet.subnet is set to 192.168.50.0.

Quote:(Still wondering why the network mask is not required input - hard to understand the interface selection procedure.)

For each adapter, the IP address is combined with the network mask and compared with the value of ohnet.subnet if set. If multiple adapters match, one of these is chosen arbitrarily.