From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from webmail.newmedia-net.de (smtps.newmedia-net.de [IPv6:2a05:a1c0:0:de::167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id DBED33B2A4 for ; Tue, 20 Aug 2019 14:12:00 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=newmedia-net.de; s=mikd; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=WuX5T/NswmDn3d6uzsXKtodn52qyRtcyHaqQrg4eUPs=; b=s5o4EJSmWwDYrl4DW7ENe03qJbXLC8Ha/iEsH8m6u0ObQfX7xCSlCSRMRw+ZdiapiVUgm23wwnftK/Q9d9ayiLKqL3a7YtLqq9axM7pX/pdgTc80a4s+TOHK/QhGDRasrkapUO/wOPnOPMkQd6M+yDZ6ifcACtWtiMDKI2WrEBA=; To: =?UTF-8?Q?Toke_H=c3=b8iland-J=c3=b8rgensen?= , Dave Taht Cc: "cake@lists.bufferbloat.net >> Cake List" 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> From: Sebastian Gottschall Message-ID: <74bccc2b-b805-255f-b6a7-83ade9af6765@newmedia-net.de> Date: Tue, 20 Aug 2019 20:10:57 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <87tvabsp99.fsf@toke.dk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Received: from [2003:c9:3f25:1300:e947:ab73:1d88:4792] by webmail.newmedia-net.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from ) id 1i08c3-0007cx-89; Tue, 20 Aug 2019 20:12:07 +0200 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:12:01 -0000 >> 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 need >> 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 Sebastian