From: Sebastian Moeller <moeller0@gmx.de>
To: "jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>,
jf--- via Bloat <bloat@lists.bufferbloat.net>,
Rich Brown <richb.hanover@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: [Bloat] Re: LibreQoS CLI - in OpenWrt?
Date: Wed, 29 Jul 2026 19:38:05 +0200 [thread overview]
Message-ID: <3D0596FC-A417-4EAD-9504-4E78B414C430@gmx.de> (raw)
In-Reply-To: <65E60C6E-827F-42AB-B96B-B15A9F976C2F@jonathanfoulkes.com>
Hi there...
On July 29, 2026 6:46:19 PM GMT+02:00, jf--- via Bloat <bloat@lists.bufferbloat.net> wrote:
>Agree, it is very cool; it’s on my to-do list to replace the speedtestcpp package with this. I run a test every two hours on my x86 router. That test hits the Ookla infrastructure, but the target server selection seems simplistic, and results are quite variable (or my ISP has +/- 500Mbps variances across a week).
Just to keep in mind (I am certain you are aware, but others on the list might not) someone typically has to pay for such servers and their capacity/traffic, so I would ask the LibreQoS guys first whether they consider automated repeated tests fair use (even thougb every 12 hours is rather tame).
>
>One question I have is: Does this test account for *all* traffic flowing through the router during the tests, or solely on its own payloads?
This test can only account for its own traffic... but you can combine it it monitoring your wan interfaces traffic counters, no?
>
>Ideally, as a CLI running on the router itself, it should capture 100% of the bidirectional traffic so its reports are accurate. If one or more nodes in the network are streaming video, that could be a significant delta.
Sure, but that is a different use case to this bufferbloat test... IMHO the libreqos test is primarily interested in measuring bufferbloat, not capacity, it mostly uses the data transfers to saturate the link to allow meaningfull loaded latency measurements.
>
>The IQtests we ran on the IQrouter took all traffic into consideration, and it made a difference.
Sure, different usecase, I guess.
>
>Cheers,
>
>Jonathan
>
>> On Jul 29, 2026, at 12:30 PM, Rich Brown <richb.hanover@gmail.com> 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/
>>
>> 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).
>>
>> Has anyone tested this on OpenWrt? Or considered adding this as a package? (This would be a fun project, but I’m up to my elbows in stuff right now...)
>>
>> Rich
>> _______________________________________________
>> Bloat mailing list -- bloat@lists.bufferbloat.net
>> To unsubscribe send an email to bloat-leave@lists.bufferbloat.net
>
>_______________________________________________
>Bloat mailing list -- bloat@lists.bufferbloat.net
>To unsubscribe send an email to bloat-leave@lists.bufferbloat.net
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2026-07-29 17:38 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 [this message]
2026-07-29 16:54 ` Matt Taggart
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=3D0596FC-A417-4EAD-9504-4E78B414C430@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=jf@jonathanfoulkes.com \
--cc=richb.hanover@gmail.com \
/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