Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Jonas Mårtensson" <martensson.jonas@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] separate shaping of wifi
Date: Mon, 4 Feb 2019 10:18:11 +0100	[thread overview]
Message-ID: <CAM9iV=+ABQfdbyJyM8F34Bok6sMmRra46NHZgc2-riUDcBATiQ@mail.gmail.com> (raw)
In-Reply-To: <9E084747-CD0E-4729-8EFF-8625D771ED6B@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]

> Aside from fixing the end device so it isn't bloated in the first place,
I think you have a reasonable solution there.  You might only need to limit
the ingress rate on wlan0, if your router's wifi stack is debloated.

Right, only limit the ingress rate, that's what I'm doing and it seems to
be working but I haven't seen this type of setup being discussed anywhere.
The tricky part is choosing the shaping rate since the actual wifi rate
varies.

There's not so much I can do to fix bloat on windows and android devices.

/Jonas

On Sun, Feb 3, 2019 at 11:08 PM Jonathan Morton <chromatix99@gmail.com>
wrote:

> > On 4 Feb, 2019, at 12:04 am, Jonas Mårtensson <
> martensson.jonas@gmail.com> wrote:
> >
> > 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?
>
> Aside from fixing the end device so it isn't bloated in the first place, I
> think you have a reasonable solution there.  You might only need to limit
> the ingress rate on wlan0, if your router's wifi stack is debloated.
>
>  - Jonathan Morton
>
>

[-- Attachment #2: Type: text/html, Size: 2094 bytes --]

      reply	other threads:[~2019-02-04  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 22:04 Jonas Mårtensson
2019-02-03 22:08 ` Jonathan Morton
2019-02-04  9:18   ` Jonas Mårtensson [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='CAM9iV=+ABQfdbyJyM8F34Bok6sMmRra46NHZgc2-riUDcBATiQ@mail.gmail.com' \
    --to=martensson.jonas@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@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