IntenseWebs/LibreQoS
3
0
Fork 0
mirror of https://github.com/LibreQoE/LibreQoS.git synced 2025-01-08 13:33:02 -06:00
Code Issues Packages Projects Releases Wiki Activity
37b9b571ab
LibreQoS/old/v1.1
History
Dave Täht 9e984b1216 Major move around of every thing 
Clean up old versions
2022-12-07 11:04:54 -08:00
..
xdp-cpumap-tc@888cc7712f Major move around of every thing 2022-12-07 11:04:54 -08:00
graph.py Major move around of every thing 2022-12-07 11:04:54 -08:00
graphBandwidth.py Major move around of every thing 2022-12-07 11:04:54 -08:00
graphLatency.py Major move around of every thing 2022-12-07 11:04:54 -08:00
influxDBdashboardTemplate.json Major move around of every thing 2022-12-07 11:04:54 -08:00
integrationUISP.py Major move around of every thing 2022-12-07 11:04:54 -08:00
ispConfig.example.py Major move around of every thing 2022-12-07 11:04:54 -08:00
LibreQoS.py Major move around of every thing 2022-12-07 11:04:54 -08:00
lqAPI.py Major move around of every thing 2022-12-07 11:04:54 -08:00
network.example.json Major move around of every thing 2022-12-07 11:04:54 -08:00
README.md Major move around of every thing 2022-12-07 11:04:54 -08:00
scheduled.py Major move around of every thing 2022-12-07 11:04:54 -08:00
Shaper.example.csv Major move around of every thing 2022-12-07 11:04:54 -08:00

README.md

v1.1 (IPv4) (Beta)

Released: 2022

LibreQoS

Installation Guide

Features

  • Tested up to 11Gbps asymmetrical throughput in real world deployment with 5000+ clients.

  • Network hierarchy can be mapped to the network.json file. 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).

  • Graphing of bandwidth to InfluxDB. Parses bandwidth data from "tc -s qdisc show" command, minimizing CPU use.

  • Graphing of TCP latency to InfluxDB - via PPing integration.

Considerations

  • Any top-level parent node is tied to a single CPU core. Top-level nodes are evenly distributed across CPUs. Since each CPU can usually only accommodate up to 4Gbps, ensure any single top-level parent node will not require more than 4Gbps throughput.

Limitations

  • As with 0.9 and v1.0, not yet dual stack, clients can only be shaped by IPv4 address until IPv6 support is added to XDP-CPUMAP-TC. Once that happens we can then shape IPv6 as well.

  • XDP's cpumap-redirect achieves higher throughput on a server with direct access to the NIC (XDP offloading possible) vs as a VM with bridges (generic XDP).