From: Dave Taht <dave.taht@gmail.com>
To: libreqos@lists.bufferbloat.net
Subject: [LibreQoS] adapting cake to the environment
Date: Tue, 25 Oct 2022 11:25:53 -0700 [thread overview]
Message-ID: <CAA93jw4oVbZYb88h-zxiXwCONEM5Tg_h8Gye+yCSzv_mudF1Hw@mail.gmail.com> (raw)
in seeing the complaints about other products bashing on snmp too
hard, it occurred to me that some of the
currently end-user focused work here:
https://forum.openwrt.org/t/cake-w-adaptive-bandwidth/135379
Might actually also apply within an ISP to adjust the AP emulation in
libreqos based on these sorts of active measurements which require no
more than ping, or ntp messaging, to work.
I especially like the ability to use ICMP based type 13 messages which
makes it possible to calculate one way delays (OWD). There was some
branch that leveraged ntp also.
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2022-10-25 18:26 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=CAA93jw4oVbZYb88h-zxiXwCONEM5Tg_h8Gye+yCSzv_mudF1Hw@mail.gmail.com \
--to=dave.taht@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