From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: nfqueue & bridge netfilter considered broken
Date: Fri, 2 Sep 2016 11:58:53 +0200 [thread overview]
Message-ID: <20160902095853.GA5577@salvia> (raw)
In-Reply-To: <20160902090848.GA506@breakpoint.cc>
On Fri, Sep 02, 2016 at 11:08:48AM +0200, Florian Westphal wrote:
> I - discard extra nfct entry when cloning. Works, but obviously not
> compatible in any way (the clones are INVALID).
This approach is simple and it would only break when packets are
flooded to all ports, actually this is not working anyway because of
clashes at confirm, right?
next prev parent reply other threads:[~2016-09-02 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 9:08 nfqueue & bridge netfilter considered broken Florian Westphal
2016-09-02 9:58 ` Pablo Neira Ayuso [this message]
2016-09-02 10:00 ` Pablo Neira Ayuso
2016-09-02 10:22 ` Florian Westphal
2016-09-06 10:10 ` Pablo Neira Ayuso
2016-09-06 11:24 ` Florian Westphal
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=20160902095853.GA5577@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.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).