From: Ignacio Ocampo <nafiux@gmail.com>
To: libreqos@lists.bufferbloat.net
Subject: [LibreQoS] LibreQoS upstream + Cake/FQ_Codel in CPE Router?
Date: Sun, 10 Sep 2023 20:35:07 -0600 [thread overview]
Message-ID: <CAAGqNkmxrXqBcLX+v3g75Fhf1SjL=bV+BmV5YhEKcC-EutLsog@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
Hi all,
Is it recommended (or not), to run Cake/FQ_Codel in CPE routers, even if
LibreQoS is running upstream?
If so, which are the advantages? Also, I'm assuming I will have to set
up the router with a lower bandwidth than the assigned by LibreQoS?
For instance, if LibreQoS is assigning 13Mbit to the customer, the router
(with Cake or FQ_Codel) enabled need to have a limit of ~11Mbit?
Please advise. Thanks!
--
Ignacio Ocampo
[-- Attachment #2: Type: text/html, Size: 778 bytes --]
next reply other threads:[~2023-09-11 2:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 2:35 Ignacio Ocampo [this message]
2023-09-11 16:18 ` Dave Taht
2023-09-11 16:23 ` Dave Taht
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='CAAGqNkmxrXqBcLX+v3g75Fhf1SjL=bV+BmV5YhEKcC-EutLsog@mail.gmail.com' \
--to=nafiux@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