[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111004154244.3530f21c@nehalam.linuxnetplumber.net>
Date: Tue, 4 Oct 2011 15:42:44 -0700
From: Stephen Hemminger <shemminger@...tta.com>
To: Michał Mirosław <mirqus@...il.com>
Cc: Sridhar Samudrala <sri@...ibm.com>,
Andi Kleen <andi@...stfloor.org>,
Kevin Wilson <wkevils@...il.com>, netdev@...r.kernel.org
Subject: Re: [RFC] iproute2: add br command
On Wed, 5 Oct 2011 00:32:31 +0200
Michał Mirosław <mirqus@...il.com> wrote:
> 2011/10/5 Sridhar Samudrala <sri@...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@...stfloor.org> wrote:
> >> > Stephen Hemminger <shemminger@...tta.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.
--
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