netdev - Re: [RFC 0/5] bridge - introduce via_phys

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100226165104.GB5364@lenovo>
Date:	Fri, 26 Feb 2010 19:51:04 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Stephen Hemminger <shemminger@...ux-foundation.org>
Cc:	bridge@...ux-foundation.org, netdev@...r.kernel.org,
	Pavel Emelyanov <xemul@...nvz.org>,
	Denis Lunev <den@...nvz.org>
Subject: Re: [RFC 0/5] bridge - introduce via_phys_dev feature

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.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.
> 

Looks promising for me (CC'ed a few people just to be sure I'm not
missing anything).

	-- Cyrill
--
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