A Quality of Experience and Smart Queue Management system for ISPs. Leverage CAKE to improve network responsiveness, enforce bandwidth plans, and reduce bufferbloat.
Go to file
2022-10-19 14:44:47 -06:00
docs Add files via upload 2022-09-27 13:13:50 -06:00
v0.7 Delete new.txt 2021-07-01 23:53:20 -06:00
v0.8 Update README.md 2022-09-11 13:27:02 -06:00
v0.9 Update README.md 2022-09-11 13:26:34 -06:00
v1.0 Update README.md 2022-09-11 13:25:34 -06:00
v1.1 tidy, nix original config files 2022-09-13 17:04:21 +12:00
v1.2 Fix prefix handling in v1.2 2022-10-19 14:44:47 -06:00
v1.3 Update integrationSplynx.py 2022-10-19 13:26:01 -06:00
.gitignore Update .gitignore 2022-09-27 12:18:54 -06:00
.gitmodules add v1.3-alpha 2022-10-18 14:26:43 -06:00
LICENSE Initial commit 2020-10-02 09:18:14 -06:00
README.md Update README.md 2022-09-30 04:56:12 -06:00

LibreQoS

LibreQoS is a Quality of Experience and Smart Queue Management system designed for Internet Service Providers (such as Fixed Wireless Internet Service Providers) to optimize the flow of their network traffic and thus reduce bufferbloat, keep the network responsive, and improve the end-user experience.

Because customers see greater performance, ISPs receive fewer support tickets/calls and reduce network traffic from fewer retransmissions.

A sub-$1000 server running LibreQoS can shape traffic for hundreds or thousands of customers at over 10 Gbps.

Learn more at LibreQoS.io

LibreQoS

Real World Impact

By allowing ISPs to better optimize traffic flows and minimize packet loss - ISPs can ensure reliable connectivity for video calls and voice calls. With work-from-home, remote learning, and tele-medicine becoming increasingly common minimizing disruptions to video calls and VoIP can save jobs, keep students engaged, and help ensure equitable access to medical care.

Features

Flexible Hierarchical Shaping

Network hierarchy can be mapped to a json file in v1.1+. This allows for both simple network heirarchies (Site>AP>Client) as well as much more complex ones (Site>Site>Micro-PoP>AP>Site>AP>Client). This allows operators to ensure a given sites peak bandwidth will not exceed the capacity of its back-haul links (back-haul congestion control). This can allow operators to support more users on the same network equipment with LibreQoS than with competing QoE solutions which only shape by AP and Client. Shaping just by AP and client could allow for high aggregate peaks to occur on back-hauls links, which can trigger packet loss and disrupt network connectivity. LibreQoS flexible shaping provides a solution to this.

CAKE

CAKE is the product of nearly a decade of development efforts to improve on fq_codel. With the diffserv_4 parameter enabled CAKE groups traffic in to Bulk, Best Effort, Video, and Voice. This means that without having to fine-tune traffic priorities as you would with DPI products CAKE automatically ensures your clients OS update downloads will not disrupt their zoom calls. It allows for multiple video conferences to operate on the same connection which might otherwise “fight” for upload bandwidth causing call disruptions. It holds the connection together like glue.

XDP

Fast, multi-CPU queueing leveraging xdp-cpumap-tc. Tested up to 11 Gbps of real world traffic with just 30% CPU use on an Intel Xeon Gold 6254. Likely capable of 30Gbps or more.

Graphing

Graph bandwidth by client and node (Site, AP, etc), with great visalizations made possible by InfluxDB

System Requirements

  • VM or physical server. Physical server will have higher throughput (XDP vs generic XDP).
  • One management network interface, completely separate from the traffic shaping interfaces. Usually this would be the Ethernet interface built in to the motherboard.
  • Dedicated Network Interface Card
  • NIC must have two or more interfaces for traffic shaping.
  • NIC must have multiple TX/RX transmit queues. Here's how to check from the command line.
  • Ubuntu Server 22.04 or above recommended. All guides assume Ubuntu Server 21.10 or above. Ubuntu Desktop is not recommended as it uses NetworkManager instead of Netplan.
  • Kernel version 5.14 or above
  • Python 3, PIP, and some modules (listed in respective guides).
  • Choose a CPU with solid single-thread performance within your budget.

Versions

IPv4 + IPv6:

IPv4 only: