[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100226092551.25f0e50f@nehalam>
Date: Fri, 26 Feb 2010 09:25:51 -0800
From: Stephen Hemminger <shemminger@...ux-foundation.org>
To: "richardvoigt@...il.com" <richardvoigt@...il.com>
Cc: Cyrill Gorcunov <gorcunov@...il.com>, netdev@...r.kernel.org,
bridge@...ux-foundation.org
Subject: Re: [Bridge] [RFC 0/5] bridge - introduce via_phys_dev feature
On Fri, 26 Feb 2010 10:52:52 -0600
"richardvoigt@...il.com" <richardvoigt@...il.com> wrote:
> On Fri, Feb 26, 2010 at 10:18 AM, Stephen Hemminger
> <shemminger@...ux-foundation.org> wrote:
> > Looking back at this. What if the API was simpler:
> >
> > Instead of:
> >> Typical session looks like
> >>
> >> | s...@...10.0.160$ brctl addbr br0
> >> | s...@...10.0.160$ ifconfig br0 up
> >> | s...@...10.0.160$ echo 1 > /sys/class/net/bridge/br0/via_phys_dev
> >> | s...@...10.0.160$ brctl addif br0 eth0
> >> | (...waiting a bit...)
> >> | s...@...10.0.160$
> >
> > Why not:
> > 1. Setup bridge (and any other interfaces except eth0); includes bringing br0 up
> > 2. Add eth0 to bridge with new flag to inherit
> > a. brctl addif br0 eth0 inherit
> >
> > Inherit functionality would need to move address (Ether, IP, IPv6)
> > and routes from eth0 to br0.
> > I will see about doing it as much as possible in userspace.
>
> How about inheriting the up/down status as well, this way the bridge
> can be left down until the settings are inherited, and will come up
> with the inherited MAC address, IP address, and routing table instead
> of changing while live?
Ok.
--
--
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