From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jan Engelhardt <jengelh@medozas.de>,
David Miller <davem@davemloft.net>,
markmc@redhat.com, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable
Date: Wed, 01 Jul 2009 11:01:05 +0200 [thread overview]
Message-ID: <4A4B25D1.6040904@trash.net> (raw)
In-Reply-To: <20090701011528.GA28676@gondor.apana.org.au>
Herbert Xu wrote:
> On Tue, Jun 30, 2009 at 10:16:35PM +0200, Jan Engelhardt wrote:
>> It makes sense absolutely. Consider:
>>
>> * packet enters bridge
>> * NF_HOOK(PF_INET6, NF_INET_PRE_ROUTING, ...) is called by nr_netfilter.c
>> * (connection tracking entry is set up)
>> * let bridging decision be "local delivery"
>
> No, my question is does it ever make sense to use conntrack as
> part of bridge netfilter. That is, do you ever want to test it
> in your rules that are run as part of bridge netfilter.
Probably not, but thats not how its used currently. The packets are
passed to IP netfilter, which performs connection tracking. I'm not
sure how we could avoid the negative effects while still allowing this.
next prev parent reply other threads:[~2009-07-01 9:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1246379267.3749.42.camel@blaa>
2009-06-30 17:00 ` [PATCH] bridge: make bridge-nf-call-*tables default configurable Herbert Xu
2009-06-30 19:06 ` David Miller
2009-06-30 20:16 ` Jan Engelhardt
2009-06-30 20:57 ` Mark Smith
2009-06-30 21:30 ` Jan Engelhardt
2009-07-01 1:48 ` Herbert Xu
2009-07-01 1:15 ` Herbert Xu
2009-07-01 3:50 ` Jan Engelhardt
2009-07-01 4:10 ` Herbert Xu
2009-07-01 4:14 ` Ben Greear
2009-07-01 9:01 ` Patrick McHardy [this message]
2009-07-01 8:57 ` Patrick McHardy
2009-07-01 9:07 ` Herbert Xu
2009-07-01 9:21 ` Patrick McHardy
2009-07-01 16:33 ` Herbert Xu
2009-07-01 17:01 ` Patrick McHardy
2009-07-01 3:16 ` David Miller
2009-07-01 10:45 ` Mark McLoughlin
2009-07-01 10:51 ` Patrick McHardy
2009-07-01 16:02 ` David Miller
2009-07-01 16:05 ` Patrick McHardy
2009-07-01 16:08 ` David Miller
2009-07-01 21:18 ` Mark Smith
2009-07-01 16:02 ` David Miller
2009-07-01 16:26 ` Herbert Xu
2009-07-01 8:56 ` Patrick McHardy
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=4A4B25D1.6040904@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jengelh@medozas.de \
--cc=markmc@redhat.com \
--cc=netdev@vger.kernel.org \
--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).