From: Benjamin LaHaise <bcrl@kvack.org>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] net/bridge: port based vlan filtering for bridges
Date: Wed, 11 Apr 2012 11:36:29 -0400 [thread overview]
Message-ID: <20120411153629.GC17739@kvack.org> (raw)
In-Reply-To: <20120411083052.1ca6a6ef@nehalam.linuxnetplumber.net>
On Wed, Apr 11, 2012 at 08:30:52AM -0700, Stephen Hemminger wrote:
> On Wed, 11 Apr 2012 11:10:02 -0400
> Benjamin LaHaise <bcrl@kvack.org> wrote:
>
> > Hello folks,
> >
> > Attached is the first stab at a patch to make it possible to filter packets
> > received from other bridge ports based on the port number. This can be used
> > to emulate port based VLANs that some switches support.
> >
> > The justification for this is a bit interesting. Initially, I had been
> > filtering packets using firewall rules. Unfortunately, the number of
> > filter rules becomes impossible to manage when trying to filter traffic
> > between 100 different ports. CPU overhead of the filters is also a major
> > problem.
> >
> > The particular use-case I'm dealing with is simulating wireless networks
> > on a system using LXC containers. Each guest has a veth device that is a
> > member of the bridge, but the topology of which nodes can "hear" each other
> > changes at runtime.
> >
> > Comments/thoughts?
> >
>
> Nak. If firewall doesn't work then implement a better netfilter
> module.
That still results in the CPU overhead of packet duplication for each and
every bridge port regardless of the port receiving the packet or not.
Hmmmm, would a NF_HOOK in should_deliver be okay?
-ben
--
"Thought is the essence of where you are now."
next prev parent reply other threads:[~2012-04-11 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 15:10 [RFC] net/bridge: port based vlan filtering for bridges Benjamin LaHaise
2012-04-11 15:30 ` Stephen Hemminger
2012-04-11 15:36 ` Benjamin LaHaise [this message]
2012-04-11 15:38 ` Stephen Hemminger
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=20120411153629.GC17739@kvack.org \
--to=bcrl@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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