[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180523.163910.2061435036559770900.davem@davemloft.net>
Date: Wed, 23 May 2018 16:39:10 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: chromatix99@...il.com
Cc: toke@...e.dk, cake@...ts.bufferbloat.net, netdev@...r.kernel.org,
netfilter-devel@...r.kernel.org
Subject: Re: [Cake] [PATCH net-next v15 4/7] sch_cake: Add NAT awareness to
packet classifier
From: Jonathan Morton <chromatix99@...il.com>
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.
Powered by blists - more mailing lists