I'm attempting to use Suricata IDS for monitoring the network events in a specific interface. I have been able to install the service and I am able to execute it.
Everything seems to be working fine, except for the fact that the service might fail to start at computer startup.
The service in fact necessarily needs to have the connection ready and available (assigned IP, etc.) when Windows starts it.
So, the service is working correctly at startup ONLY when the network is up and running for that interface. If for some reason the network connection comes up later than usual, the service fails to start, and Windows seems to not try again to start it.
I've been looking at other stackoverflow questions in order to correctly set the dependencies for the network connection and for what I'm trying to do, but they seem to not be working.
So, what are the correct dependencies to add to my service for instructing Windows to wait for the network connection to be up and running (IP already assigned, DNS already set, etc.) before starting it?
If you have an alternative idea on how to solve the problem you're welcome to post a reply. Any suggestion is appreciated.
