From: David Lang <david@lang.hm>
To: Gabriel Ulysee Cyril Rossetti <grossetti@unicef.org>
Cc: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>,
"bloat-request@lists.bufferbloat.net"
<bloat-request@lists.bufferbloat.net>
Subject: [Cake] Re: CAKE/SQM behind ISP CPE (bridge vs non-bridge, router vs inline)
Date: Mon, 13 Apr 2026 08:10:21 -0700 (MST) [thread overview]
Message-ID: <61on70s5-53r1-p0s2-140r-0pn027657po9@ynat.uz> (raw)
In-Reply-To: <VI0PR05MB124948E57D6C845C02BED0DD8CA242@VI0PR05MB12494.eurprd05.prod.outlook.com>
remember, you are not running cake on the ISP side of the link, so by
definition, you do not have full control of your inbound traffic.
As a result, you have to shape to something below line rate as you are working
with indirect methods that are far less precise than what would be ideal.
As such, having the cpe equipment in the loop probably does not change things
noticably in terms of managing downstream traffic.
When you are managing the upstream traffic that you are directly controlling,
you can shape it very close to line rate (just make it the WAN line rate, not
the ethernet line rate to your cpe :-) )
there are things the cpe can do to hurt you, but if you can't replace it, you
can't replace it. It won't be as bad as you are fearing.
David Lang
prev parent reply other threads:[~2026-04-13 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 13:13 [Cake] CAKE/SQM behind ISP CPE (bridge vs non-bridge, router vs inline) Gabriel Ulysee Cyril Rossetti
2026-04-13 15:10 ` David Lang [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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61on70s5-53r1-p0s2-140r-0pn027657po9@ynat.uz \
--to=david@lang.hm \
--cc=bloat-request@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=grossetti@unicef.org \
/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