From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 26 Feb 2010 19:51:04 +0300 From: Cyrill Gorcunov Message-ID: <20100226165104.GB5364@lenovo> References: <20090511114639.440944109@openvz.org> <20090519152153.012d4814@nehalam> <20090520192726.GF4968@lenovo> <20090520131225.03b7715a@nehalam> <20090521180805.GC4932@lenovo> <20090521140504.1865883b@nehalam> <20090522201850.GF5354@lenovo> <20100226081843.07f37742@nehalam> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100226081843.07f37742@nehalam> Subject: Re: [Bridge] [RFC 0/5] bridge - introduce via_phys_dev feature List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stephen Hemminger Cc: Denis Lunev , netdev@vger.kernel.org, bridge@linux-foundation.org, Pavel Emelyanov On Fri, Feb 26, 2010 at 08:18:43AM -0800, Stephen Hemminger wrote: > Looking back at this. What if the API was simpler: > > Instead of: > > Typical session looks like > > > > | s...@10.10.0.160$ brctl addbr br0 > > | s...@10.10.0.160$ ifconfig br0 up > > | s...@10.10.0.160$ echo 1 > /sys/class/net/bridge/br0/via_phys_dev > > | s...@10.10.0.160$ brctl addif br0 eth0 > > | (...waiting a bit...) > > | s...@10.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. > Looks promising for me (CC'ed a few people just to be sure I'm not missing anything). -- Cyrill