Become a Beta Tester

Xen · Platform

Frabs for XCP-ng

On an XCP-ng host, Frabs lists the running domains and watches each VM's virtual interface.

Become a Beta TesterTry the Demo

XCP-ng

Protects
Xen virtual machines
Recognised by
The XCP-ng release
Watches
vif<domid>.<n>
Panel links
Not needed

How it works

How Frabs works on XCP-ng

  1. 01

    Install

    One command as root on the server. It reads the setup without changing anything.

  2. 02

    Recognise XCP-ng

    The XCP-ng release tells the sensor which platform it is on.

  3. 03

    Find every guest

    xl list for each running domain.

  4. 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

vif<domid>.<n>

One per VM network device, for example vif12.0

Bridges. The bridges your VMs attach to. Bridges with no VMs 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

PlatformXCP-ng
Watchesvif12.0, …
Leaves aloneBridges with no guests
Changes madeNone until you act

Get started

Install on XCP-ng

On the server, as root

curl -fsSL https://install.frabs.net | sh -s -- --token frb_...

Questions

Is anything installed inside the VMs?
No. The sensor runs on the server itself, never inside a customer's guest.
Does Frabs change my bridges or firewall?
No. It counts traffic in its own nftables table on each guest interface, and only acts when your rules or your team say so.
What happens if I add a bridge or move guests?
The server's page shows that the layout changed. Run frabs reconnect, review the updated plan and confirm.
What if the sensor stops?
Its network changes are removed and traffic carries on, unless you chose fail-closed.

Also supported

Other platforms

See it with real data

Become a Beta TesterTry the Demo