Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Thibaut" <hacks@slashdirt.org>
To: "Jonathan Morton" <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Trouble with CAKE
Date: Fri, 13 Dec 2019 14:13:34 +0000	[thread overview]
Message-ID: <5ec3c68f6c3ce1d2614104655e6ed15a@slashdirt.org> (raw)
In-Reply-To: <8FC615C8-4885-4F0A-B2EE-934DC4E806E8@gmail.com>

Hi Jonathan,

Thanks for the quick reply.

December 13, 2019 3:02 PM, "Jonathan Morton" <chromatix99@gmail.com> wrote:

>> On 13 Dec, 2019, at 3:43 pm, Thibaut <hacks@slashdirt.org> wrote:
>> 
>> I've been using CAKE on my DSL-connected Linux router for the last few years, and it worked well
>> until very recently. Two things happened:
>> 
>> 1) My ISP (French "Free") switched my DSLAM to native IPv6, which for the time being means that I
>> had to revert to using their set-top-box (Freebox) instead of the VDSL2 model I was using in bridge
>> mode until then (CAKE in "bridged-ptm ether-vlan" mode)
>> 2) I upgraded my router from 3.16 (Devuan Jessie) to 4.9 (Devuan ASCII)
>> 
>> Since then, no matter which setup I use, I cannot get CAKE to work as intended. Specifically, any
>> long-standing best effort stream (such as a remote rsync) will be throttled to a near grinding halt
>> even though there is no other significant traffic going on. Some random bursts can be seen (with
>> iftop) but nothing ever gets close to half the maximum bandwidth. This is notably affecting the
>> OpenWRT buildbots I'm hosting on this link.
> 
> Old kernels, including 4.9 series, tend to be more problematic than the latest ones. If you can, I
> would recommend updating to a 5.x series kernel, in which Cake is an upstream feature. I won't
> presume to guess how best to achieve that with your distro.

Indeed. Given this is a relatively "security-sensitive" setup, I'd rather not diverge from distro (or run "unstable" for that matter).
Still, CAKE was previously working Just Fine(TM) on an even older kernel: 3.16...
 
> The good news is that Free.fr is among the relatively few ISPs who have actively tackled
> bufferbloat themselves. As a workaround while you sort this out, you should get reasonable
> performance just from using the Freebox directly.

Well, probably not with the antiquated Freebox model I have: a v5. I would also very much like to drop it to be able to connect again at VDSL2 speeds (I was getting 50/10 instead of the current 20/1) and save 75% on power usage (the Freebox is power hungry). But that's orthogonal to the current issue :)

What I could do for a test is temporarily revert back to the previous 3.16/Jessie setup (I have kept a backup) and see if I can reproduce the same behavior there, in which case I think that would definitely point in the general direction of a bad interaction with the Freebox tunnel?

Best,
Thibaut

  parent reply	other threads:[~2019-12-13 14:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 13:43 Thibaut
2019-12-13 14:02 ` Jonathan Morton
2019-12-13 22:39   ` Thibaut
2019-12-13 22:40     ` Thibaut
2019-12-13 23:52       ` Thibaut
2019-12-14  9:50         ` Jonathan Morton
2019-12-14 10:01           ` Thibaut
2019-12-14 10:35             ` Kevin 'ldir' Darbyshire-Bryant
2019-12-14 10:56               ` Kevin 'ldir' Darbyshire-Bryant
2019-12-14 11:59                 ` Thibaut
2019-12-14 12:07                   ` Thibaut
2019-12-14 12:09                   ` Jonathan Morton
2019-12-14 12:11                     ` Thibaut
2019-12-14 12:59                       ` Toke Høiland-Jørgensen
2019-12-14 14:04                         ` Thibaut
2019-12-14 21:35                           ` Toke Høiland-Jørgensen
2019-12-13 14:13 ` Thibaut [this message]
2019-12-13 14:15 ` Sebastian Moeller
2019-12-13 14:21 ` Thibaut
2019-12-13 18:44   ` Thibaut

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=5ec3c68f6c3ce1d2614104655e6ed15a@slashdirt.org \
    --to=hacks@slashdirt.org \
    --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