From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Westphal Subject: Re: nft synproxy integration Date: Mon, 9 Nov 2015 23:29:53 +0100 Message-ID: <20151109222953.GC7759@breakpoint.cc> References: <20151109163015.GM8098@macbook.localdomain> <8670E62A-489B-41B4-A89B-AAF740264ACA@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jozsef Kadlecsik , pablo@netfilter.org, netfilter-devel@vger.kernel.org, bjornar.ness@gmail.com To: Patrick McHardy Return-path: Received: from Chamillionaire.breakpoint.cc ([80.244.247.6]:55214 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751033AbbKIW37 (ORCPT ); Mon, 9 Nov 2015 17:29:59 -0500 Content-Disposition: inline In-Reply-To: <8670E62A-489B-41B4-A89B-AAF740264ACA@trash.net> Sender: netfilter-devel-owner@vger.kernel.org List-ID: Patrick McHardy wrote: > Am 9. November 2015 19:36:06 GMT+00:00, schrieb Jozsef Kadlecsik : > >On Mon, 9 Nov 2015, Patrick McHardy wrote: > >> The method of using notrack would of course still be possible. > > > >I like the idea: the notrack method would still be supported and the > >"do > >conntrack but with safety-net" way would be possible too. Looks cool! > > Thanks Jozsef. I'm thinking it's the best of both worlds myself. Implementation should be quite easy, I'll give it a try. I'm fine with the suggestion, but, pardon the heretic question: Why do we need synproxy after the recent listen lock removal from Eric?