From: "Jonas Mårtensson" <martensson.jonas@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] separate shaping of wifi
Date: Sun, 3 Feb 2019 23:04:50 +0100 [thread overview]
Message-ID: <CAM9iV=JDpOTp2PUjnE26OMxq2fgOGFh7gMbm5tiCkWnDZ9miJw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
I'm running OpenWrt with sqm on my home router. Is there any potential
problem with enabling sqm with cake on both eth0 (wan) and wlan0? The
reason for doing this is that if I only do shaping on the wan interface I
still get bad uplink bufferbloat on wifi. I assume this is because the
bottleneck in this case is actually the wifi and the bloat is in the end
device (laptop, phone, etc.). By shaping to a rate lower than the wifi
rate, the bloat disappears. Is there any better way to accomplish this than
to enable a second sqm instance on wlan0 if I don't want to sacrifice speed
for wired devices?
/Jonas
[-- Attachment #2: Type: text/html, Size: 665 bytes --]
next reply other threads:[~2019-02-03 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 22:04 Jonas Mårtensson [this message]
2019-02-03 22:08 ` Jonathan Morton
2019-02-04 9:18 ` Jonas Mårtensson
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='CAM9iV=JDpOTp2PUjnE26OMxq2fgOGFh7gMbm5tiCkWnDZ9miJw@mail.gmail.com' \
--to=martensson.jonas@gmail.com \
--cc=cake@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