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] New devblog: Dynamic Circuits - Part 1
Date: Mon, 20 Apr 2026 22:35:39 +0200	[thread overview]
Message-ID: <CAJUtOOjL8=CDK7dNAVKf7ViUTwarEqeSEMkTkWan27_t5PpRvQ@mail.gmail.com> (raw)

Hello to all,

When we finished removing the reload penalty, we unblocked a lot of
development options - many of them features people have been wanting for a
long time. The most recent is dynamic circuits:


*https://devblog.libreqos.com/posts/0016-dynamic-circuits1/
<https://devblog.libreqos.com/posts/0016-dynamic-circuits1/>*

Previously, when LibreQoS spotted traffic from an IP address that didn’t
appear in ShapedDevices.csv, it listed it as an “Unknown IP” - and didn’t
really let you do a lot with it. It was up to you to figure out what it
was, what it’s doing. It was subject to traffic shaping, but was put into a
big “unknown” bucket - shaped collectively. We’ve offered a few workaround
over the years, which can help - but they aren’t really what people want.
For example, declaring “Fallback subnets” with a shared “unknown pool” of
bandwidth can help a lot. It’s also led to some wasteful design - if you
know public WiFi can occupy 254 IP addresses but each needs individual
shaping, you might have been tempted to create 254 circuits - whether or
not you needed them.


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-04-20 20:31 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='CAJUtOOjL8=CDK7dNAVKf7ViUTwarEqeSEMkTkWan27_t5PpRvQ@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