thebracket / libreqos Goto Github PK

LibreQoS is a Quality of Experience and Smart Queue Management system designed for 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.

Servers running LibreQoS can shape traffic for many thousands of customers.

Learn more at LibreQoS.io

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 site’s 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 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.

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.

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

• UISP (v1.2+)
• Splynx (v1.3+)

• VM or physical server
  • For VMs, NIC passthrough is required for optimal throughput and latency (XDP vs generic XDP). Using Virtio / bridging is much slower than NIC passthrough. Virtio / bridging should not be used for large amounts of traffic.

• 2 or more CPU cores
• A CPU with solid single-thread performance within your budget.
  • For 10G+ throughput on a budget, consider the AMD Ryzen 9 5900X or Intel Core i7-12700KF
• CPU Core count required assuming single thread performance of 2700 or more:

(* Estimated)

• Mimumum RAM = 2 + (0.002 x Subscriber Count) GB
• Recommended RAM:

(* Estimated)

• 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 for Shaping Interfaces
  • NIC must have 2 or more interfaces for traffic shaping.
  • NIC must have multiple TX/RX transmit queues. Here's how to check from the command line.
  • Known supported cards:
    • NVIDIA Mellanox MCX512A-ACAT
    • Intel X710
    • Intel X520

• v1.2.1-stable
• v1.3-alpha

• v1.1
• v1.0