Traffic Shaping

Control congestion through the network hierarchy

LibreQoS combines explicit shared-capacity limits, per-circuit queue management, and an eBPF/XDP packet path on your own server.

Deploy LibreQoS Queueing design

Give the shared bottleneck its own limit

Illustrative download limits, not sizing recommendations. Active circuits compete within each configured parent limit, even when their individual plan rates add up to more.

01Shared backhaul: 500 Mbps
An explicit limit on this part of the configured path.
02Site: 300 Mbps
An explicit limit on this part of the configured path.
03Access parent: 200 Mbps
An explicit limit on this part of the configured path.
04Competing circuits: 100 Mbps each
CAKE manages competing flows within each circuit.

Set capacity where it is shared

Represent the real topology with nested queue classes rather than applying only a network-wide limit.

Backhaul, site, AP, and OLT parents
Circuit min/max rates
Visible configured and effective limits

Keep competing flows fair

CAKE manages queues inside each circuit, helping interactive traffic remain responsive while bulk transfers continue.

Per-flow fairness
Active queue management
TCP and UDP traffic share the queue discipline

Use the Linux packet-processing path

eBPF and XDP support packet classification and forwarding at scale. Validate CPU, NIC support, and topology against your target workload.

Supported x86 hardware
XDP-capable shaping NICs
Queue and CPU visibility during a pilot

Why packet ordering matters

A busy download shouldn't make a call wait. Toggle CAKE to see how separate flow queues and congestion feedback help keep traffic responsive.

Operator workflow

Read throughput and queue delay together

Watch the circuit view under load. Throughput alone does not show whether queueing delay is controlled; compare it with RTT and queue behavior over the same interval.