From: Benny Amorsen <benny+usenet@amorsen.dk>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
bridge@lists.linux-foundation.org
Subject: Re: [Bridge] RFC: Simple Private VLAN impl.
Date: Sat, 13 Jun 2009 01:54:30 +0200 [thread overview]
Message-ID: <m3eitpovnt.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: <OFB9321502.79301BE7-ONC12575D3.0075D3D1-C12575D3.00765847@transmode.se> (Joakim Tjernlund's message of "Fri\, 12 Jun 2009 23\:32\:39 +0200")
Joakim Tjernlund <joakim.tjernlund@transmode.se> writes:
> But why should I not be able to add both 4043 and 4044 to the same bridge?
Of course you should. And they should behave as a proper bridge, letting
packets flow as they were meant to. Unless you decide that local policy
does not permit packets to flow freely, and then you use ebtables to
apply that local policy.
> I just sent a patch to add split horizon support to the linux bridge. Have
> a look. More power to the linux bridge that way.
You have already been shown that you can achieve what you want with the
existing kernel code, at the cost of a somewhat complicated rule setup.
You have also been shown ways to simplify this rule setup.
I really hope that your patches are not accepted. Sorry if this is
harsh, but the company I work for has in the past depended on the
flexibility of the existing code. While that company is currently
migrating to proprietary solutions because PC's don't get faster at the
rate which traffic grows, it seems ridiculous that Linux should copy the
limitations of less capable platforms.
/Benny
next prev parent reply other threads:[~2009-06-12 23:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 13:32 [Bridge] RFC: Simple Private VLAN impl Joakim Tjernlund
2009-06-10 14:45 ` Stephen Hemminger
2009-06-10 15:32 ` Joakim Tjernlund
2009-06-10 16:27 ` Ross Vandegrift
2009-06-10 17:09 ` Joakim Tjernlund
[not found] ` <OF4422F49E.33BDAF5C-ONC12575D1.005C802A-C12575D1.005E38A3@LocalDomain>
2009-06-11 12:50 ` Joakim Tjernlund
2009-06-11 14:22 ` Ross Vandegrift
2009-06-11 14:48 ` Joakim Tjernlund
2009-06-11 16:12 ` Ross Vandegrift
2009-06-11 19:43 ` Joakim Tjernlund
2009-06-11 21:04 ` Benny Amorsen
2009-06-11 23:10 ` Joakim Tjernlund
2009-06-11 23:44 ` Ross Vandegrift
2009-06-11 19:51 ` Daniel Robbins
2009-06-11 23:58 ` Ross Vandegrift
2009-06-12 0:15 ` Daniel Robbins
2009-06-12 3:56 ` Ross Vandegrift
2009-06-12 9:17 ` Benny Amorsen
2009-06-12 9:41 ` Joakim Tjernlund
2009-06-12 9:48 ` Benny Amorsen
2009-06-12 11:03 ` Marek Kierdelewicz
2009-06-12 11:45 ` Joakim Tjernlund
2009-06-12 12:52 ` Ross Vandegrift
2009-06-12 13:09 ` Joakim Tjernlund
2009-06-12 13:19 ` richardvoigt
2009-06-12 13:47 ` Joakim Tjernlund
2009-06-12 19:31 ` richardvoigt
2009-06-12 21:32 ` Joakim Tjernlund
2009-06-12 23:54 ` Benny Amorsen [this message]
2009-06-13 14:58 ` Joakim Tjernlund
2009-06-13 4:29 ` richardvoigt
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=m3eitpovnt.fsf@ursa.amorsen.dk \
--to=benny+usenet@amorsen.dk \
--cc=bridge@lists.linux-foundation.org \
--cc=joakim.tjernlund@transmode.se \
--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