From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F22493B2A4 for ; Tue, 20 Aug 2019 14:49:22 -0400 (EDT) Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 08DF5C055673 for ; Tue, 20 Aug 2019 18:49:22 +0000 (UTC) Received: by mail-ed1-f72.google.com with SMTP id u3so4668559edm.13 for ; Tue, 20 Aug 2019 11:49:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=5K/Wjtf+Cf1AllF7LHMu1I5QA6cdMcu2S9fteY/U3fE=; b=pQqgkOA3fK1QKzlQZ8r2EIVzB7rPU5Qc+VNkGbSm8RWUiah3xgtUa2sJWHHDEMfpCk vQzPaxmMqkk5lNixG4CZWDw29o6Wwu9wg3ShfTCV4z9Rm9Ght2jQMA+VcwyX0zrqBew2 gBJ6c1Sgffs19kbdcrINeKxVWEmkZ/AXJRRX11KsAVpAV9Sn1bnW23c+lQ+bKeaLqa6C D7s9vl6Fc1tlvsE8lmOThTmFFxf9kKWCq7XON6LDhDT3oRUOr7gfrXr2c6YdSMEcqYmA x/GkqNS6dXcVy2nrWYVm4hHGsb1mOs3K1xmFntcESDZyWnOPksmtVmwuGptAMPl5VFtl ucMQ== X-Gm-Message-State: APjAAAXkwH3nEPULLmPZx1psR4SEClQEH3sbWeUX/P8GkCTplGtAVhUG 78NehcKqQOftQLxzbXZCul+R4RmDzmI0jvVsebAvdqG1eA3b3k2DKc9YXZzR/SbvmAjeMqueUcT S9CIXhv9m9FkXqJKGGILNlg== X-Received: by 2002:aa7:d153:: with SMTP id r19mr25126396edo.68.1566326960798; Tue, 20 Aug 2019 11:49:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqxEYoG+eVqoVUaWUsDZ15tMW7aS4GSKAFI17NjFRCnlh5u5IWTr2S+8CxD3hWqo9S7c61Bdpw== X-Received: by 2002:aa7:d153:: with SMTP id r19mr25126383edo.68.1566326960645; Tue, 20 Aug 2019 11:49:20 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([2a00:7660:6da:443::2]) by smtp.gmail.com with ESMTPSA id gz5sm2718519ejb.21.2019.08.20.11.49.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Aug 2019 11:49:19 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 51818181CE4; Tue, 20 Aug 2019 20:49:19 +0200 (CEST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Sebastian Gottschall , Dave Taht Cc: "cake\@lists.bufferbloat.net \>\> Cake List" In-Reply-To: References: <384866b4-4c91-cf2c-c267-ee4036e5fbf7@newmedia-net.de> <87wof7sriw.fsf@toke.dk> <6782ec15-30eb-63b0-f54f-376c5e6b840b@newmedia-net.de> <87tvabsp99.fsf@toke.dk> <74bccc2b-b805-255f-b6a7-83ade9af6765@newmedia-net.de> <87r25fsn70.fsf@toke.dk> X-Clacks-Overhead: GNU Terry Pratchett Date: Tue, 20 Aug 2019 20:49:19 +0200 Message-ID: <87o90jsmds.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] cake in dd-wrt X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2019 18:49:23 -0000 Sebastian Gottschall writes: > Am 20.08.2019 um 20:31 schrieb Toke H=C3=B8iland-J=C3=B8rgensen: >> Sebastian Gottschall writes: >> >>>>> we are already using filters. yes. its just that cake is acting always >>>>> as root and we have different sorts of qos configurations. so you have >>>>> wan. but we may have multiple lan interfaces with individual qos >>>>> settings. the same for mac / ip based user settings. so in fact we ne= ed >>>>> to create a individual qdisc for each of these setting types in worst >>>>> case, but in that case we cannot take in account the global available >>>>> bandwidth anymore. >>>> Ah, right, I see. So this is things like users wanting to limit a >>>> specific type of traffic to a certain bandwidth? >>> basicly yes. there are multiple ways. plain traffic shaping by local >>> interface name, by local mac, by local ip/net >>> and in addition there is shaping by port based or dpi based packet >>> detection and since each instance of cake doesnt know of any other >>> use of cake qdiscs its getting complicated. but we just started with >>> working on it. i'm sure i find a solution for it >> Do let us know if you do :) >> >> However, I'd also point out that when running CAKE a lot of these kinds >> of setups become simply redundant. For home networks most of the setups >> I have seen with such rule-based shaping is simply there to paper over >> the underlying bufferbloat issue. Once you solve that you don't really >> need all the policy-based stuff. > its not just about policy to get all managed. but the point is that a=20 > heavy bittorrent downloader will still steal the bandwidth of my scp=20 > session. This is indeed a concern sometimes, yeah, and actually this exact case is the original motivation for the host-based fairness feature in CAKE :) > so its about control and not just about the flow management > is about limiting ports to a specific bandwidth. for instance. i have a=20 > concert venue and i limit the backstage network to a certain maximum=20 > rate since a need a budged for other networks > so i limit the ethernet port of this network on the main router to lets=20 > say 10 mbit or something like that priorize torrent and other bad=20 > services to bulk. which just works good for internet. > so we have enough bandwidth on our other cables for doing 4k streams. > dd-wrt is not just used on these plastic routers for home users. this is= =20 > one option and works great without much qos configuration. you're right.= =20 > but if its turning more complex and professional > its not enough anymore. Sure, but those are not CAKE's target audience, so to speak. I'm not saying those use cases are not legitimate, I'm just saying you may find it difficult to shoe-horn CAKE into them; which is kinda deliberate... >> Now, there are of course exceptions to this where a strict rule-based >> shaping *is* really needed; but HTB already provides this in the kernel, >> and we don't want to re-invent that, so I'm not sure we'll ever support >> this properly in CAKE, sadly... > this is what we are also doing. cake is finally just a option. you can=20 > select multiple schedulers at the gui. including codel. fq_codel,=20 > fq_codel_fast, cake , pie etc. Right. What are you setting as the default, BTW? -Toke