Configuring Port Mirroring and Suricata IDS Firewall on Proxmox VE
7 hours ago
- The author set up an IDS using Suricata and EveBox on a Proxmox VE (PVE) host to monitor and analyze internal network traffic, addressing security concerns from unexplained activity observed in Netdata.
- The setup involves creating a Debian 12 LXC container with two network interfaces: one for normal access (eth0 on vmbr0) and one for port mirroring (eth1 on a new vmbr1 bridge), where vmbr1 carries mirrored traffic from vmbr0.
- Port mirroring is achieved using tc (traffic control) commands on the PVE host to duplicate all traffic from vmbr0 to vmbr1, with a script that must be re-run when new VMs or containers are added.
- Suricata is compiled from source and configured to listen on eth1, using its default rule set downloaded via suricata-update, with systemd service and logrotate for managing the eve.json log output.
- EveBox is installed as a frontend to consume Suricata events, run via systemd, storing data in a SQLite database with automatic rotation (7 days or 15 GB), and provides a web dashboard for event inspection.
- The solution offers enterprise-grade traffic analysis with DPI but is noted for its simplicity, low resource usage, and compared to complex alternatives like FortiGate and Sophos, which were found less satisfactory.
- The article includes practical configuration details, such as systemd service files and config adjustments, to help readers replicate the setup.