IntenseWebs/LibreQoS
3
0
Fork 0
mirror of https://github.com/LibreQoE/LibreQoS.git synced 2024-11-26 02:00:15 -06:00
Code Issues Packages Projects Releases Wiki Activity
781fb06171
LibreQoS/v1.1
History
Warren 27c8ea2387 tidy, nix original config files
2022-09-13 17:04:21 +12:00
..
xdp-cpumap-tc@888cc7712f Added the submodule to the project. 2022-03-02 06:20:40 -07:00
graph.py Update graph.py 2022-02-14 15:38:50 -07:00
graphBandwidth.py typo correction 2022-09-12 01:38:23 -06:00
graphLatency.py update to use config vars 2022-05-16 12:04:20 +12:00
influxDBdashboardTemplate.json Add files via upload 2022-02-26 20:27:24 -07:00
integrationUISP.py minor/pep related adjustments 2022-06-21 10:48:50 +12:00
ispConfig.example.py tidy, nix original config files 2022-09-13 17:04:21 +12:00
LibreQoS.py v1.1 now in beta 2022-09-05 07:57:50 -06:00
lqAPI.py Add files via upload 2022-04-24 14:25:26 -06:00
network.example.json add ignores/dirty so the branch stays clean/_more_ pullable in prod 2022-09-13 16:52:08 +12:00
README.md Update README.md 2022-09-11 13:32:26 -06:00
scheduled.py minor/pep related adjustments 2022-06-21 10:48:50 +12:00
Shaper.example.csv add ignores/dirty so the branch stays clean/_more_ pullable in prod 2022-09-13 16:52:08 +12: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).