From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from chameleon.ash.relay.mailchannels.net (chameleon.ash.relay.mailchannels.net [23.83.222.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id BF8593B2A4 for ; Fri, 3 Feb 2017 11:42:23 -0500 (EST) X-Sender-Id: netnames|x-authuser|sagermail@sager.me.uk Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 629BE14378C for ; Fri, 3 Feb 2017 16:42:19 +0000 (UTC) Received: from smtp3.easily.co.uk (unknown [100.96.13.205]) by relay.mailchannels.net (Postfix) with ESMTPA id B642A143FB4 for ; Fri, 3 Feb 2017 16:42:18 +0000 (UTC) X-Sender-Id: netnames|x-authuser|sagermail@sager.me.uk Received: from smtp3.easily.co.uk (smtp3.easily.co.uk [172.20.104.49]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.7.14); Fri, 03 Feb 2017 16:42:19 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: netnames|x-authuser|sagermail@sager.me.uk X-MailChannels-Auth-Id: netnames X-MC-Loop-Signature: 1486140139095:2313130610 X-MC-Ingress-Time: 1486140139095 Received: from [81.2.83.97] (port=36520 helo=mainserver.wc) by smtp3.easily.co.uk with esmtpa (Exim 4.43) id 1cZgwC-0001I8-SC for cake@lists.bufferbloat.net; Fri, 03 Feb 2017 16:42:16 +0000 Received: from localhost ([127.0.0.1]) by mainserver.wc with esmtp (Exim 4.86_2) (envelope-from ) id 1cZgwC-0004jX-9N for cake@lists.bufferbloat.net; Fri, 03 Feb 2017 16:42:16 +0000 References: <1010949359.501064.1485874182374@webmail.strato.de> <6BA19F35-E3BB-48C4-9010-2153908E1DFA@gmail.com> To: Cake List From: John Sager X-Enigmail-Draft-Status: N1110 Message-ID: Date: Fri, 3 Feb 2017 16:42:15 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <6BA19F35-E3BB-48C4-9010-2153908E1DFA@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-AuthUser: sagermail@sager.me.uk Subject: Re: [Cake] conntrack lookup continuation 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: Fri, 03 Feb 2017 16:42:24 -0000 I would support this. It would allow cake to behave pretty much as I have HTB+fq_codel currently set up for both egress and ingress (via ifb0) on my border router/firewall. I fwmark egress traffic based on various criteria using ip[6]tables & transfer the marks to conntrack where they are recovered on ingress to classify inbound responses to outbound requests. It would also classify inbound traffic better if cake could use fwmarks in that way as diffserv is currently pretty much useless for that purpose with most ISPs. John On 31/01/17 21:14, chromatix99 at gmail.com (Jonathan Morton) wrote: >> On 31 Jan, 2017, at 16:49, Felix Resch wrote: >> >> Since we now already do the conntrack-lookup for the nat keyword, would it be >> expensive to implement a kind of internal conntrack-mark-and-restore by cake-tin? >> >> E.g. when traffic leaves throu canke tin#x, the conntrack entry will get a fwmark and return traffic is put in the corresponding tin/bin on the ingress cake. > > That's an interesting idea. At this point I don't know how easy it is to implement, though. > > Certainly we need to clean up some other things first. > > - Jonathan Morton > >