Interfaces were handled globally before this commit. Now
alerts can be configured per-interface. So for example alerts
for the same host 193.168.2.1 can be handled differently on multiple interfaces.
Old alerts configured should be automatically migrated thanks to script startup.lua
This commits also paves the way to introduce stateful alerts in the professional version
This change is propaedeutic to Professional commit:
commit 1e1d453a1e96cc4394a0b94a7efe0b5857b1b1eb
Author: Simone Mainardi <simonemainardi@gmail.com>
Date: Mon Jul 18 20:04:53 2016 +0200
Improves the usability of historical charts
An excerpt of the json returned is:
{"srv.ip":"a.b.c.d","cli.port":50559,"srv.port":443,
"cli2srv.tcp_flags":{"SYN":1,"RST":0,"PSH":1,"FIN":0,"URG":0,"ACK":1},"cli2srv.throughput_bps":0,"bytes":2869,"srv2cli.throughput_bps":0,"cli2srv.throughput_pps":0,
"srv2cli.tcp_flags":{"SYN":1,"RST":0,"PSH":1,"FIN":0,"URG":0,"ACK":1},"tcp_established":true,"srv2cli.throughput_pps":0,"cli.ip":"192.168.2.130","proto.ndpi_id":126,"proto.ndpi":"SSL.Google"},
Clicking on flow details (e.g., protocol or src or dst)
automatically redirects the user to the db explorer page
and preserves selection details (pro version).
Database updates are now performed asynchronously.
The web server starts but notifies the user with a
'please wait' message until the updates are completed.
No queries that search for range of hosts in MySQL are
currently available. For this reason, historical tabs are hidden
from the view and will be re-enabled in the future.
Method scanAlerts was called inside a loop over the interfaces in minute.lua.
Since scanAlerts was looping over the interfaces as well, this was causing
interfaces to be deselected from the outer loop.
This commit fixes the issues by forcing scanAlerts to receive an input interface.
Fixes#582
Preferences set automatically trigger an update of
the class Preferences() members to make sure they are up
to date.
Additionally, the housekeeping frequency has been made customizable.
