From: Ben Greear <greearb@candelatech.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
David Miller <davem@davemloft.net>,
markmc@redhat.com, netdev@vger.kernel.org, kaber@trash.net,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] bridge: make bridge-nf-call-*tables default configurable
Date: Tue, 30 Jun 2009 21:14:40 -0700 [thread overview]
Message-ID: <4A4AE2B0.7060909@candelatech.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0907010535170.6438@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Wednesday 2009-07-01 03:15, 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.
>>
>
> There is the possibility that some users have -m conntrack in their
> mangle table in the PREROUTING chain. However, I am pretty sure that
> if there are such users, they do it because of the layer-3/4/5/7 part
> and not care about bridge so much.
>
>
>> conntrack is inherently a security hole when used as part of
>> bridging, because it ignores the Ethernet header so two unrelated
>> connections can be tracked as one.
>>
>
> On secondary thought, one could also argue that because conntrack
> ignores the interface, two unrelated connections happening to be routed
> through the same machine(*) are tracked as one, too.
>
I had a similar problem while trying to implement virtual routers using
different
routing tables and something like 'veth' to connect them.
My solution was to add a 'mark' field to the netdevice and allow
user-space to set
the mark on the device. This mark was included as part of the
connection identifier.
The mark is set before the pkt hits the bridge code on ingress, so a pkt
entering from
eth1 can get a different connection hash from a pkt entering eth2, even
if all other
data in the packet is the same.
I'll dig it out of my monster patch if something like this is deemed
useful upstream.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2009-07-01 4:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1246379267.3749.42.camel@blaa>
[not found] ` <20090630170027.GA22691@gondor.apana.org.au>
2009-06-30 19:06 ` [PATCH] bridge: make bridge-nf-call-*tables default configurable 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 [this message]
2009-07-01 9:01 ` 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=4A4AE2B0.7060909@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--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).