[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <513A0109.4040607@redhat.com>
Date: Fri, 08 Mar 2013 10:17:29 -0500
From: Vlad Yasevich <vyasevic@...hat.com>
To: Stephen Hemminger <stephen@...workplumber.org>
CC: netdev@...r.kernel.org, bridge@...ts.linux-foundation.org
Subject: Re: [RFC PATCH v2 net-next 0/3] Allow bridge to function in non-promisc
mode
On 03/08/2013 12:43 AM, Stephen Hemminger wrote:
> On Thu, 7 Mar 2013 16:28:45 -0500
> Vlad Yasevich <vyasevic@...hat.com> wrote:
>
>> The series adds an ability to configure the bridge into a non-primiscuous
>> mode. Instead, it provides the ability to identitfy some set of bridge
>> ports as uplinks and allows for MAC addresses to be programmed onto
>> those ports. In case the port hardware does not support mac filter,
>> that port will be placed in promiscuous mode.
>>
>> Default bridge operation continues to remain as "promiscuous". The new
>> functionality has to be enabled via sysfs (similar to other bridge extensions).
>>
>> The uplink mode is implemented as a flag on a bridge port. The api to
>> change that flag follows the existing api to enable/disable other existing
>> flags.
>>
>> All comments are welcome.
>>
>
> Can we make this a one step process and less visible to the user.
> If user defines an uplink device, and the uplink device is capable of filtering
> (and what ever other pre-conditions people can think of), then the bridge will
> transparently switch to uplink/non-promisc mode. This can also be used to trigger
> edge only mode in RSTP in the future.
>
> Less knobs.
>
Ok. Let me see what I can do.
Thanks
-vlad
--
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