Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] LibreQoS v2.2 is out!
Date: Wed, 19 Aug 2026 22:16:07 +0200	[thread overview]
Message-ID: <CAJUtOOjLb6wuiuEXVyCNR=c4p6E2OzFVa7zYE=J_4nNvMabODg@mail.gmail.com> (raw)

Hello to all,

Almost 5 months of work, we are so happy to ship v2.2!

https://github.com/LibreQoE/LibreQoS/releases/tag/v2.2

<https://github.com/LibreQoE/LibreQoS/releases/tag/v2.2>
TL;DR: The Biggest Upgrades

*Go from fresh install to running system with guided first-run setup.* A
temporary, protected setup page helps create the first admin, choose
interfaces and operating mode, preview network changes, enable HTTPS, and
hand control to the normal LibreQoS services.

*Build and manage topology visually. *The new Topology Manager gives
operators a clear workspace for reviewing sites, changing parent
relationships, finding unmapped items, and publishing a safe network layout.

*See actual traffic, not only queued traffic. *Key dashboards, circuit
pages, tree views, Insight data, and API responses can now distinguish
traffic offered to a queue from traffic that was actually transmitted.
Operators can compare subscriber demand with delivered throughput.

*Create subscriber circuits from RADIUS sessions.* LibreQoS can listen for
RADIUS accounting events and dynamically add, update, and remove subscriber
circuits for PPPoE and other session-based networks.

*Finish subscriber setup with a clear source-of-truth choice.* After the
core system starts, the new Complete Setup page guides operators to a
built-in CRM/NMS integration, an in-house importer, or manual subscriber
files.

*Run with stronger security by default. *Web access now requires
authentication, login attempts are rate limited, browser security rules are
tighter, and sensitive session details receive better protection.

*Troubleshoot faster.* StormGuard diagnostics, topology probes, clearer
warnings, effective-rate explanations, and stronger reload reporting help
operators find the cause of a problem without guessing.

*Import cleaner subscriber and topology data.* UISP, VISP, Sonar, Splynx,
Netzur, and MikroTik workflows now cover more account layouts and handle
subscriber matching more reliably.

*Keep service steady during changes.* Queue reloads, topology publishing,
WebUI recovery, and background work received extensive reliability
improvements designed to reduce interruptions and lockups.

*Plan upgrades with Insight evidence.* New circuit and site reports flag
plan-limit pressure, historical ASN views show traffic sources, geographic
maps show site location, and multi-shaper accounts keep one connected view.

*Build better tools with the LibreQoS API.* The API adds combined circuit
views, richer CAKE statistics, Quality of Outcome data, actual transmitted
throughput, and named local API keys.

Happy upgrading!

All the best,

Frank

Frantisek (Frank) Borsik


*In loving memory of Dave Täht: *1965-2025

https://libreqos.io/2025/04/01/in-loving-memory-of-dave/


https://www.linkedin.com/in/frantisekborsik

Signal, Telegram, WhatsApp: +421919416714

iMessage, mobile: +420775230885

Skype: casioa5302ca

frantisek.borsik@gmail.com

                 reply	other threads:[~2026-08-19 20:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJUtOOjLb6wuiuEXVyCNR=c4p6E2OzFVa7zYE=J_4nNvMabODg@mail.gmail.com' \
    --to=frantisek.borsik@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox