From: Stephen Hemminger <shemminger@vyatta.com>
To: "Michał Mirosław" <mirqus@gmail.com>
Cc: Sridhar Samudrala <sri@us.ibm.com>,
Andi Kleen <andi@firstfloor.org>,
Kevin Wilson <wkevils@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [RFC] iproute2: add br command
Date: Tue, 4 Oct 2011 15:42:44 -0700 [thread overview]
Message-ID: <20111004154244.3530f21c@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAHXqBF+gXg=EAOm4F_qGWhND6EsZHzoamE8fRX6eqe1p1zU-SQ@mail.gmail.com>
On Wed, 5 Oct 2011 00:32:31 +0200
Michał Mirosław <mirqus@gmail.com> wrote:
> 2011/10/5 Sridhar Samudrala <sri@us.ibm.com>:
> > On Tue, 2011-10-04 at 14:07 -0700, Stephen Hemminger wrote:
> >> On Tue, 04 Oct 2011 09:58:55 -0700
> >> Andi Kleen <andi@firstfloor.org> wrote:
> >> > Stephen Hemminger <shemminger@vyatta.com> writes:
> >> > > This adds a new 'br' command which is the bridging equivalent of
> >> > > the ip command. More of a demo of how to use netlink and bridging
> >> > > at this point.
> >> > Please name it "bridge", not "br"
> >> Ok, but it breaks the existing pattern.
> > Is this supposed to replace brctl utility?
> >
> > Can we add/delete a bridge and add/delete interfaces to a bridge using
> > this command?
> >
> > If so, why not make it
> > ip bridge add/del <brname>
> > ip bridge addif/delif <brname> <ifname>
>
> I'll add one more idea:
>
> ip link add/del <brname> type bridge
> ip bridge add/del <brname> <ifname>
> ip bridge fdb ...
In 3.0 you can already do:
# ip link add dev br3 type bridge
# ip link set dev eth3 master br3
I see no reason to add 'ip bridge' syntax wrappers.
next prev parent reply other threads:[~2011-10-04 22:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGXs5wWeFcyHQ4vO562pTOdqLNEKrJwES3W_hFF_M2reNoe1rA@mail.gmail.com>
2011-10-04 16:34 ` [RFC] iproute2: add br command Stephen Hemminger
2011-10-04 16:58 ` Ben Hutchings
2011-10-04 21:08 ` Stephen Hemminger
2011-10-04 16:58 ` Andi Kleen
2011-10-04 21:07 ` Stephen Hemminger
2011-10-04 22:17 ` Sridhar Samudrala
2011-10-04 22:27 ` Stephen Hemminger
2011-10-04 22:32 ` Michał Mirosław
2011-10-04 22:42 ` Stephen Hemminger [this message]
2011-10-04 22:54 ` Sridhar Samudrala
2011-10-04 23:00 ` Stephen Hemminger
[not found] <4E8BE29A.9070100@us.ibm.com>
[not found] ` <4E8BE63F.4020706@us.ibm.com>
2011-10-05 15:58 ` Stephen Hemminger
2011-10-05 23:00 ` Sridhar Samudrala
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=20111004154244.3530f21c@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=andi@firstfloor.org \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
--cc=wkevils@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.