Quote from: packetmangler on May 04, 2020, 04:45:25 pmEDIT: I'm doing forward and reverse lookups on the firewall for all addresses on my local network and it appears that the graphs are indeed populating with host names where IP addresses were earlier. So now the question is how often should that run?Hi @packetmangler, With release 1.5, cache time to live is 8 hours. (higher with 1.4) So, could be every 6 hours so that it replenishes the cache.
EDIT: I'm doing forward and reverse lookups on the firewall for all addresses on my local network and it appears that the graphs are indeed populating with host names where IP addresses were earlier. So now the question is how often should that run?
Disregard, I was able to address the issue.Installed Sensei and subscibed but stuck at "waiting for database service to come up." Any suggestions as I have tried w/ out success.I reinstalled elasticsearch5 w/ out success.Thanks
Sensei runs on inner-facing interfaces and determines the "remote" / "local" properties in terms of where the connection is initiated. If it comes from the LAN side, than the src ip address is considered local and dst ip address is regarded as "remote". So if a connection is from a local host behind network A to a host behind local network B, sensei will consider the host on local network B as "remote", since for the context of the connection, it was the "remote end". Obviously this is creating a bit confusion. Let us give this a bit of thought.
super stupid question:Once I enable the app control i have a few websites i can't access anymore.Is there a way to whitelist these as exception?i'm using engine version 1.5 and App & Rules DB Version: 1.5.20200501062917