eBPF Firewall

Enforce network rules near the Linux packet-processing path. Host agents coordinate kernel programs and policy maps, while the control plane provides configuration and enforcement visibility.

KernelControl planeNetwork rulesPacketsInboundHost agentUpdates mapsBPF mapsRule storeXDP and TCPacket hooksXDP_PASSXDP_DROPKernelLookupControl planeNetwork rulesHost agentUpdates mapsBPF mapsRule storeXDP and TCPacket hooksPacketsInboundXDP_PASSXDP_DROP
  • Rule update
  • Allowed packet
  • Dropped packet

What it provides

  • XDP filtering at the network interface and supported TC attachment points.
  • Address, protocol, and port policies for the services on a host.
  • Supported source-rate controls and kernel-map enforcement.
  • Central configuration with host-level network and enforcement events.

How to use it

  1. Deploy a Linux host agent with the required privileges, kernel support, and BTF.
  2. Connect it to the project using a provisioned client certificate and review program attachment status.
  3. Configure firewall policies for the intended interfaces and validate connectivity before broad enforcement.
Deploy host agentPrivileges, kernel, BTFConnect itClient certificateSet policiesValidate before enforcingDeploy host agentPrivileges, kernel, BTFConnect itClient certificateSet policiesValidate before enforcing
  • Order of the steps

Configuration and operation

Use the project Firewall and Hosts pages to inspect agent state and configure supported network controls. Native XDP attachment depends on the network driver; actual performance depends on mode, hardware, and policy.

Limits

eBPF is Linux-specific and requires compatible kernel capabilities. Packet filtering cannot interpret every application behavior or replace L7 inspection. Carefully scope network policies to avoid disrupting administrative or application traffic.