Flexible Hierarchical Shaping
(Back-haul Congestion Mitigation)
Operators map their network hierarchy in LibreQoS. This enables both simple network hierarchies (Site>AP>Client) as well as much more complex ones (Site>Site>Micro-PoP>AP>Site>AP>Client). This can be used to ensure that a given site’s peak bandwidth will not exceed the capacity of its back-haul links (back-haul congestion control). Operators can support more users on the same network equipment with LibreQoS than with competing QoE solutions which only shape by AP and Client.
LibreQoS offers multi-CPU IP filtering via two XDP programs – xdp-cpumap-tc and cpumap-pping. XDP (the eXpress Data Path) allows for high-performance packet processing that can integrate cooperatively with the Linux kernel.
CAKE is the product of nearly a decade of development efforts to improve on fq_codel. With the diffserv4 parameter enabled – CAKE groups traffic in to Bulk, Best Effort, Video, and Voice. This means that without having to fine-tune traffic priorities – 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. With work-from-home, remote learning, and tele-medicine becoming increasingly common – minimizing video call disruptions can save jobs, keep students engaged, and help ensure equitable access to medical care.
Graph metrics including:
- Circuit Plan / Node Utilization
- DiffServ Tin Selection
- TCP Latency
IPv4 & IPv6
Support for assigning IPv4 addresses and subnets, as well as IPv6 prefixes of arbitrary length.
- Full Topology Mapping (Site, AP, Micro-PoP, etc)
- Client Mapping
- Client Mapping
Need another CRM Integrated? Please take our poll here so we know which to prioritize.
|Oregon||H.B. 4155||Regulation||State Contracts|
|Vermont||S.B. 289||Regulation||State Contracts|
|Washington||H.B. 2282||Regulation||All ISPs|
|Hawaii||Executive Order 18-02||Executive Order||State Contracts|
|Montana||Executive Order 3-2018||Executive Order||State Contracts|
|New Jersey||Executive Order 9||Executive Order||All ISPs|
|New York||Executive Order 175||Executive Order||State Contracts|
|Rhode Island||Executive Order 18-02||Executive Order||State Contracts|
|Maine||LD 1364||Regulation||State Contracts|
LibreQoS is Free and Open Source software (Libre software) licensed under the GPLv2.
Open source projects have the advantage that many developers are able to see the code – then catch and correct bugs that would otherwise be overlooked in closed-source development projects.
Most closed-source QoE platforms are built on open source foundations – fq_codel, CAKE, HTB, XDP, DPDK, and eBPF. Closed-source QoE developers have to develop their platforms completely disconnected from the community of developers which created the underlying framework of their platforms. There is important information lost there, and the absence of information exchange means that implementation errors go undetected.
LibreQoS has benefited from feedback by the original authors of fq_codel, CAKE, and XDP – allowing us to catch and correct implementation errors promptly. If a closed-source QoE solution has implementation mistakes or missed opportunities for optimization – who will catch that? An open source project saves everyone time and effort in this regard.
Unlike most commercial QoE solutions, the LibreQoS project collaborates with the open source projects which make it possible (Linux, XDP, CAKE, eBPF, Rust). When you participate in the LibreQoS project, you are strengthening the long term development of its upstream projects, particularly XDP and CAKE – which will shape the future of the internet, and hopefully create a better internet for billions of users around the world.