From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sam Vilain Subject: Re: strict isolation of net interfaces Date: Fri, 30 Jun 2006 14:49:05 +1200 Message-ID: <44A49121.4050004@vilain.net> References: <44A1689B.7060809@candelatech.com> <20060627225213.GB2612@MAIL.13thfloor.at> <1151449973.24103.51.camel@localhost.localdomain> <20060627234210.GA1598@ms2.inr.ac.ru> <20060628133640.GB5088@MAIL.13thfloor.at> <1151502803.5203.101.camel@jzny2> <44A44124.5010602@vilain.net> <44A450D1.2030405@fr.ibm.com> <20060630023947.GA24726@sergelap.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Cedric Le Goater , hadi@cyberus.ca, Herbert Poetzl , Alexey Kuznetsov , viro@ftp.linux.org.uk, devel@openvz.org, dev@sw.ru, Andrew Morton , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Andrey Savochkin , Daniel Lezcano , Ben Greear , Dave Hansen , Alexey Kuznetsov , "Eric W. Biederman" Return-path: Received: from watts.utsl.gen.nz ([202.78.240.73]:30385 "EHLO watts.utsl.gen.nz") by vger.kernel.org with ESMTP id S1750810AbWF3Csk (ORCPT ); Thu, 29 Jun 2006 22:48:40 -0400 To: "Serge E. Hallyn" In-Reply-To: <20060630023947.GA24726@sergelap.austin.ibm.com> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Serge E. Hallyn wrote: > The last one in your diagram confuses me - why foo0:1? I would > have thought it'd be > > host | guest 0 | guest 1 | guest2 > ----------------------+-----------+-----------+-------------- > | | | | > |-> l0 <-------+-> lo0 ... | lo0 | lo0 > | | | | > |-> eth0 | | | > | | | | > |-> veth0 <--------+-> eth0 | | > | | | | > |-> veth1 <--------+-----------+-----------+-> eth0 > | | | | > |-> veth2 <-------+-----------+-> eth0 | > > [...] > > So conceptually using a full virtual net device per container > certainly seems cleaner to me, and it seems like it should be > simpler by way of statistics gathering etc, but are there actually > any real gains? Or is the support for multiple IPs per device > actually enough? > Why special case loopback? Why not: host | guest 0 | guest 1 | guest2 ----------------------+-----------+-----------+-------------- | | | | |-> lo | | | | | | | |-> vlo0 <---------+-> lo | | | | | | |-> vlo1 <---------+-----------+-----------+-> lo | | | | |-> vlo2 <--------+-----------+-> lo | | | | | |-> eth0 | | | | | | | |-> veth0 <--------+-> eth0 | | | | | | |-> veth1 <--------+-----------+-----------+-> eth0 | | | | |-> veth2 <-------+-----------+-> eth0 | Sam.