Minimserver takes long to show up

[simoncn]

(20-06-2015 10:48)tarnkappe Wrote:  IGMP is activated for wifi and I can deactivate this. (I will test if this will be an advantage for the different upnp apps that I am using.) But as the hardwired uniti does not see the minimserver, too, I tried to find out if the two routers have IGMP activated for their LAN ports. This is difficult as I could not find a clear statement. It seems that at least the fritz box has IGMP enabled. For the asus router I could not find an information. Also I could not find an option in both routers to de/activate it for LAN.

Does a multicast member (an UPnP server) not have a chance to send an IGMP "here I am" package after starting up but has to wait for a IGMP query from the current IGMP master? Maybe ohNet should send such SSDP alive packages for a while until it received an IGMP package.

As far as I understand, IGMP is a good thing that one should have enabled, because it lowers the number of network packages flooding around with multicast traffic. It would be a pity if UPnP conflicts with this conceptionally.

There is no conflict between IGMP snooping and UPnP/SSDP. I am running my network with IGMP snooping enabled and UPnP/SSDP working correctly. This took a long time and a lot of learning/experimentation to achieve.

If you want to keep IGMP snooping enabled, you will need to add your DS213+ as a fixed manual entry to the SSDP multicast group in the switch or router to which it is connected. You will need to do the same for this switch or router all the way back to the master router (the IGMP querier). This will prevent the DS213+ from being dropped from the SSDP multicast group when it enters deep sleep mode.

ohNet doesn't know about IGMP messages or multicast group membership because these are handled by a lower layer in the operating system. I'm not sure whether ohNet can detect that the NAS has entered "deep sleep" mode. This would depend on whether ohNet receives a notification from the operating system that the network adapter has been disabled/enabled. If ohNet doesn't receive such a notification, it wouldn't be able to detect that the NAS has awoken from deep sleep and know that an SSDP "alive" notification needs to be sent.

I don't have a NAS that can enter "deep sleep" mode in this way. If you would like to produce a MinimServer debug log from your NAS, I will look at it and let you know what is happening inside ohNet. Please do the following:

1) Stop and restart MinimServer from the Package Center
2) Make sure that MinimServer is visible on the network
3) In the Properties window, set the ohnet.debug property to All-Timer
4) In the log window, set the logging level to Debug
5) Close the log window
6) Allow the DS213+ to enter deep sleep mode and note the time
7) Awaken the DS213+ from deep sleep mode and note the time
8) In File Station, navigate to the MinimServer > appData folder and copy the minimserver.log file to minimserver1.log
9) Reset the ohnet.debug property and the logging level to their original values
10) Zip the minimserver1.log file and attach it to a post here together with the times of entering and leaving deep sleep mode. Please let me know if the zipped file is too large to attach.