From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Bart De Schuymer <bdschuym@pandora.be>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: [PATCH:RFC 5/5] bridge-netfilter: use the vlan id as part of the connection tracking tuple for bridged traffic
Date: Wed, 31 Mar 2010 12:17:06 +0200 [thread overview]
Message-ID: <4BB32122.8070101@plouf.fr.eu.org> (raw)
In-Reply-To: <1269962855.10116.15.camel@edumazet-laptop>
Eric Dumazet a écrit :
>
> This really sounds very strange, layering violation or something.
Isn't the whole bridge-netfilter concept already a layering violation by
design ?
> You mix conntracking, bridge and vlan here.
>
> Why setups without bridge should not care of vlan + conntracking side
> effects ?
Because without bridge, the host is attached at the IP layer level to
the VLANs, so their IP ranges are not supposed to overlap.
Anyway your objection applies to hosts with multiple bridges without
VLAN so the bridges may see overlapping IP ranges. Conntrack zones with
a dedicated target seems a more generic approach.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-03-31 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 14:16 [PATCH:RFC 5/5] bridge-netfilter: use the vlan id as part of the connection tracking tuple for bridged traffic Bart De Schuymer
2010-03-30 15:27 ` Eric Dumazet
2010-03-31 8:35 ` Patrick McHardy
2010-04-01 11:02 ` Bart De Schuymer
2010-04-01 11:06 ` Patrick McHardy
2010-03-31 10:17 ` Pascal Hambourg [this message]
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=4BB32122.8070101@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=bdschuym@pandora.be \
--cc=eric.dumazet@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=shemminger@linux-foundation.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).