[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20121213.140023.2131448980265576282.davem@davemloft.net>
Date: Thu, 13 Dec 2012 14:00:23 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: shemminger@...tta.com
Cc: vyasevic@...hat.com, or.gerlitz@...il.com, netdev@...r.kernel.org,
mst@...hat.com, john.r.fastabend@...el.com
Subject: Re: [PATCH 00/11] Add basic VLAN support to bridges
From: Stephen Hemminger <shemminger@...tta.com>
Date: Thu, 13 Dec 2012 09:47:19 -0800
> On Wed, 12 Dec 2012 18:36:38 -0500
> Vlad Yasevich <vyasevic@...hat.com> wrote:
>
>> On 12/12/2012 05:54 PM, Or Gerlitz wrote:
>> > On Wed, Dec 12, 2012 at 10:01 PM, Vlad Yasevich <vyasevic@...hat.com> wrote:
>> >> This series of patches provides an ability to add VLANs to the bridge
>> >>
>
> The bigger question is why is this impossible or too awkward with existing
> netfilter (ebtables) functionality? As a practical matter, I like to keep
> the bridging code as simple as possible and move the complexity away from
> the core.
>
> Also, if the functionality lived in netfilter rules, the developer and user
> would have a more freedom to implement complex rulesets.
I do not consider it wise to create more, rather then fewer, users
of ebtables.
It is one of the most poorly constructed subsystems in the entire
networking.
Just my $0.02
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists