From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::8]) (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 26A2D3BA8D for ; Tue, 31 Jan 2017 09:49:43 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1485874182; l=374; s=domk; d=beif.de; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject:To:From: Date; bh=NqKsjU/mxC35EGlcgjgSDtByVvCbxhoEJw5VGCdpMk4=; b=fr5PifTJDGjLztUAyupGdf4dd/YslZuEdnpW5eNfDJysldyxe7N166BzmB84JXaB9d eOcRIxUYBCGuBBrKC0eGAJwQw/mjL76EWn0KQPOvHTCHJupkhAsF94f2YQyzxE+4nGyI CT9FsLrJd71oYDnAvM6vnf49Wo19sg3U5658Q= X-RZG-AUTH: :KnkIeUW6W/3IemYYXDgPNPmQkn5u2CeXaMvbclqq0nNMErNFXNRHpZk= X-RZG-CLASS-ID: mo00 Received: from oxapp06-03.back.ox.d0m.de (com4.strato.de [81.169.145.237]) by smtp-ox.front (RZmta 39.12 AUTH) with ESMTPSA id Z006d3t0VEngC8v (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (curve X9_62_prime256v1 with 256 ECDH bits, eq. 3072 bits RSA)) (Client did not present a certificate) for ; Tue, 31 Jan 2017 15:49:42 +0100 (CET) Date: Tue, 31 Jan 2017 15:49:42 +0100 (CET) From: Felix Resch To: cake@lists.bufferbloat.net Message-ID: <1010949359.501064.1485874182374@webmail.strato.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Medium X-Originating-Client: open-xchange-appsuite X-Mailer: Open-Xchange Mailer v7.8.2-Rev20 X-Mailman-Approved-At: Tue, 31 Jan 2017 10:47:59 -0500 Subject: [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: Tue, 31 Jan 2017 14:49:44 -0000 Hoi! (longtime lurker here) 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. cheers felix