From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shards.monkeyblade.net (shards.monkeyblade.net [184.105.139.130]) (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 D5C513B29E for ; Wed, 23 May 2018 16:39:12 -0400 (EDT) Received: from localhost (pool-173-77-163-54.nycmny.fios.verizon.net [173.77.163.54]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 0E2E9144E93BE; Wed, 23 May 2018 13:39:10 -0700 (PDT) Date: Wed, 23 May 2018 16:39:10 -0400 (EDT) Message-Id: <20180523.163910.2061435036559770900.davem@davemloft.net> To: chromatix99@gmail.com Cc: toke@toke.dk, cake@lists.bufferbloat.net, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org From: David Miller In-Reply-To: <370B23D9-E929-4A73-BB7C-C1BE4A01C7E6@gmail.com> References: <91739F64-20B7-4C56-A7A3-AB8C71B9437C@gmail.com> <20180523.160403.20551254565100734.davem@davemloft.net> <370B23D9-E929-4A73-BB7C-C1BE4A01C7E6@gmail.com> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Wed, 23 May 2018 13:39:11 -0700 (PDT) Subject: Re: [Cake] [PATCH net-next v15 4/7] sch_cake: Add NAT awareness to packet classifier 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: Wed, 23 May 2018 20:39:13 -0000 From: Jonathan Morton Date: Wed, 23 May 2018 23:33:04 +0300 > Now I'm *really* confused. > > Are you saying that the user has to set up their own conntrack > mechanism using extra userspace commands? Because complicating the > setup process that way runs directly counter to Cake's design > philosophy. I mean not anything filtering or firewall related. We have a full flow dissector in the networking core, which often runs on every RX packet anyways. Record what we need and use it on egress after NAT has occurred.