KVM · Platform
Frabs for SolusVM
On a SolusVM slave, Frabs reads KVM guests through libvirt and OpenVZ containers through vzlist.
SolusVM
- Protects
- KVM virtual machines and OpenVZ containers
- Recognised by
- The solusvm package
- Watches
- Each VM's tap device · veth<ctid>.<n> or venet0
- Panel links
- Open in SolusVM
How it works
How Frabs works on SolusVM
- 01
Install
One command as root on the server. It reads the setup without changing anything.
- 02
Recognise SolusVM
The solusvm package tells the sensor which platform it is on.
- 03
Find every guest
A read-only libvirt connection: virsh list and domiflist. vzlist.
- 04
You confirm
You review what it will watch. Protection starts within 30 seconds of confirming.
Networking
What it watches, and what it leaves alone
Each VM's tap device
As libvirt reports it
veth<ctid>.<n> or venet0
For containers; venet0 traffic is split by container address
Bridges. The bridges your guests attach to. Bridges with no guests are left alone.
How traffic is counted. A Frabs-only nftables table on each guest interface. Your own firewall rules and the host's interfaces are not touched, and nothing changes until a rule or a person acts.
An example plan
Get started
Install on SolusVM
On the server, as root
curl -fsSL https://install.frabs.net | sh -s -- --token frb_...
- Install on each slave node, not the master
- VM pages link straight to the VM: Open in SolusVM
- Read the Install Guide
Questions
Is anything installed inside the VMs?
Does Frabs change my bridges or firewall?
What happens if I add a bridge or move guests?
What if the sensor stops?
Also supported
