From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N66g8-0007RL-Nt for qemu-devel@nongnu.org; Thu, 05 Nov 2009 13:03:24 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N66g2-0007GF-VN for qemu-devel@nongnu.org; Thu, 05 Nov 2009 13:03:23 -0500 Received: from [199.232.76.173] (port=57416 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N66g2-0007Fh-On for qemu-devel@nongnu.org; Thu, 05 Nov 2009 13:03:18 -0500 Received: from moutng.kundenserver.de ([212.227.17.10]:49976) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N66g2-0007I5-17 for qemu-devel@nongnu.org; Thu, 05 Nov 2009 13:03:18 -0500 From: Arnd Bergmann Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for qemu Date: Thu, 5 Nov 2009 19:02:46 +0100 References: <1257294485-27015-1-git-send-email-aliguori@us.ibm.com> <200911051820.48878.arnd@arndb.de> <4AF30E7A.5020708@us.ibm.com> In-Reply-To: <4AF30E7A.5020708@us.ibm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200911051902.46415.arnd@arndb.de> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Mark McLoughlin , Arnd Bergmann , Juan Quintela , Dustin Kirkland , qemu-devel@nongnu.org, Michael Tsirkin , Avi Kivity On Thursday 05 November 2009, Anthony Liguori wrote: > > How about abstracting it further and not making the helper depend on > > bridge code. If we put the helper into netcf, we could make that > > a more generic '-net netcf,helper=/usr/bin/netcf-helper' target, > ... > > Whether qemu-bridge-helper should live in qemu is another point to think > about. I think I would like to start with it being in qemu but then > hope someone else pulls it into a separate project along with tunctl. So how about putting your qemu-bridge-helper into qemu for the -net bridge wrapper, but makeing -net netcf default to a different wrapper that we put into netcf? The netcf version can then be extended with advanced features like routing and macvlan modes, as well as more sophisticated integration into the distro's access control infrastructure. Arnd <><