From: Toshiaki Makita <makita.toshiaki@lab•ntt.co.jp>
To: Vlad Yasevich <vyasevic@redhat•com>, netdev@vger•kernel.org
Cc: john.r.fastabend@intel•com, shemminger@vyatta•com,
bridge@lists•linux-foundation.org, jhs@mojatatu•com,
mst@redhat•com
Subject: Re: [PATCH net-next 0/8] Non-promisc bidge ports support
Date: Thu, 15 May 2014 22:02:25 +0900 [thread overview]
Message-ID: <5374BAE1.1050607@lab.ntt.co.jp> (raw)
In-Reply-To: <5374B934.1060902@lab.ntt.co.jp>
(2014/05/15 21:55), Toshiaki Makita wrote:
> (2014/05/15 0:09), Vlad Yasevich wrote:
>> This series adds functionality to the bridge device to enable
>> operations without setting all ports to promiscuous mode.
>>
>> The basic concept is this. The bridge keeps track of the ports
>> that support learning and flooding packets to unknown destinations.
>> We call these ports auto-discovery ports since they automatically
>> discover who is behind them through learning and flooding.
>>
>> If flooding and learning are disabled via flags, then the port
>> requires static configuration to tell it which mac addresses
>> are behind it. This is accomplished through adding of fdbs.
>> These fdbs should be static as dynamic fdbs can expire and systems
>> will become unreachable due to lack of flooding.
>
> Hi Vlad,
>
> This is not a comment for this patch set, but I have a question.
>
> I'm trying to use bridge command to turn off flood/learning but couldn't
> find the corresponding command.
> I'm expecting something like "bridge link set br0 flood/learning".
>
> Are there any other userspace commands that can set flood/learning flag?
>
I've just found them in sysfs. Sorry for noise, thanks.
Toshiaki Makita.
prev parent reply other threads:[~2014-05-15 13:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 15:09 [PATCH net-next 0/8] Non-promisc bidge ports support Vlad Yasevich
2014-05-14 15:09 ` [PATCH net-next 1/8] bridge: Turn flag change macro into a function Vlad Yasevich
2014-05-14 15:09 ` [PATCH net-next 2/8] bridge: Keep track of ports capable of automatic discovery Vlad Yasevich
2014-05-14 15:40 ` Stephen Hemminger
2014-05-14 15:42 ` Stephen Hemminger
2014-05-15 16:04 ` Vlad Yasevich
2014-05-14 15:09 ` [PATCH net-next 3/8] bridge: Add functionality to sync static fdb entries to hw Vlad Yasevich
2014-05-14 20:47 ` Sergei Shtylyov
2014-05-14 15:09 ` [PATCH net-next 4/8] bridge: Introduce BR_PROMISC flag Vlad Yasevich
2014-05-14 15:09 ` [PATCH net-next 5/8] bridge: Add addresses from static fdbs to non-promisc ports Vlad Yasevich
2014-05-14 20:44 ` Sergei Shtylyov
2014-05-14 15:09 ` [PATCH net-next 6/8] bridge: Automatically manage port promiscuous mode Vlad Yasevich
2014-05-14 15:09 ` [PATCH net-next 7/8] bridge: Correctly manage promiscuity when user requested it Vlad Yasevich
2014-05-14 15:09 ` [PATCH net-next 8/8] bridge: Automatically manage promisc mode when vlan filtering is on Vlad Yasevich
2014-05-14 20:41 ` Sergei Shtylyov
2014-05-14 15:21 ` [PATCH net-next 0/8] Non-promisc bidge ports support Michael S. Tsirkin
2014-05-14 19:29 ` David Miller
2014-05-15 16:09 ` Vlad Yasevich
2014-05-15 12:55 ` Toshiaki Makita
2014-05-15 13:02 ` Toshiaki Makita [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=5374BAE1.1050607@lab.ntt.co.jp \
--to=makita.toshiaki@lab$(echo .)ntt.co.jp \
--cc=bridge@lists$(echo .)linux-foundation.org \
--cc=jhs@mojatatu$(echo .)com \
--cc=john.r.fastabend@intel$(echo .)com \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
--cc=vyasevic@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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