From: Patrick McHardy <kaber@trash.net>
To: Florian Westphal <fw@strlen.de>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
pablo@netfilter.org, netfilter-devel@vger.kernel.org,
bjornar.ness@gmail.com
Subject: Re: nft synproxy integration
Date: Tue, 10 Nov 2015 02:05:20 +0000 [thread overview]
Message-ID: <20151110020519.GA5514@macbook.localdomain> (raw)
In-Reply-To: <20151109222953.GC7759@breakpoint.cc>
On 09.11, Florian Westphal wrote:
> Patrick McHardy <kaber@trash.net> wrote:
> > Am 9. November 2015 19:36:06 GMT+00:00, schrieb Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>:
> > >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?
Simple answer is - its for the network, not for the host :)
next prev parent reply other threads:[~2015-11-10 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 16:30 nft synproxy integration Patrick McHardy
[not found] ` <CAJO99T=4fjPkBTFEYuibGsHe=BfM0KRbhYkP_E_RPa49SUWeHg@mail.gmail.com>
2015-11-09 17:25 ` Fwd: " Bjørnar Ness
2015-11-09 17:35 ` Patrick McHardy
2015-11-09 19:36 ` Jozsef Kadlecsik
2015-11-09 20:13 ` Patrick McHardy
2015-11-09 22:29 ` Florian Westphal
2015-11-10 2:05 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-19 22:30 Alexander Meinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151110020519.GA5514@macbook.localdomain \
--to=kaber@trash.net \
--cc=bjornar.ness@gmail.com \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).