From: Matt Taggart <matt@lackof.org>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Re: LibreQoS CLI - in OpenWrt?
Date: Wed, 29 Jul 2026 09:54:16 -0700 [thread overview]
Message-ID: <462c2fb2-eaa8-48b5-bc72-6113b5e5cf10@lackof.org> (raw)
In-Reply-To: <9CB6FF5C-601F-43B4-963F-CD2B4098ED12@gmail.com>
On 7/29/26 9:30 AM, Rich Brown wrote:
>
>> On Jul 27, 2026, at 02:03, bloat-request@lists.bufferbloat.net wrote:
>>
>> It was asked for by QoO guys for their IETF 126 Vienna Hackathon, but it
>> will be useful for everyone, so it was added to the speedtest website now:
>>
>> https://test.libreqos.com/cli/
The direct URL the installer uses for linux/x86_64 is
https://download.libreqos.com/cli/latest/libreqos-test-linux-x86_64
it's a dynamically linked executable that only uses base system
libraries, no additional dependencies.
How is it licensed and is the source somewhere?
I did find this
https://github.com/LibreQoE/LibreQoS
It's not clear if the cli stuff is in there yet.
I look forward to this being packages in distros so I can install it
everywhere!
> This is cool, indeed. I wonder if it would be a suitable replacement for my `betterspeedtest.sh` script in OpenWrtScript (https://github.com/richb-hanover/OpenWrtScripts#betterspeedtestsh).
I love betterspeedtest.sh and appreciate it existing and will continue
to use it even if there are alternatives.
But I know a big part of making it available is actually making the
backend servers it uses for testing available. I guess this new libreqos
cli tool uses the same infra as their web based tester, is that
documented somewhere?
Matt
prev parent reply other threads:[~2026-07-29 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <178513222851.1604.3077360125516323841@gauss>
2026-07-29 16:30 ` [Bloat] Re: LibreQoS CLI - in OpenWrt? Rich Brown
2026-07-29 16:46 ` jf
2026-07-29 17:38 ` Sebastian Moeller
2026-07-29 16:54 ` Matt Taggart [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462c2fb2-eaa8-48b5-bc72-6113b5e5cf10@lackof.org \
--to=matt@lackof.org \
--cc=bloat@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