From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Wray Subject: Re: Other additional vnet questions Date: Thu, 10 Feb 2005 10:22:18 +0000 Message-ID: <420B35DA.2080705@hpl.hp.com> References: <1107965719.9884.237.camel@master.vms.security> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <1107965719.9884.237.camel@master.vms.security> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: bgb@nt-nv.com Cc: xen-devel List-Id: xen-devel@lists.xenproject.org B.G. Bruce wrote: > Some other questions I have about vnets. > > 1) Can one vif belong to more than one vnet at the same time? Think of a vnet as a virtual lan. Just as an interface can only be connected to one lan, a virtual interface can only be connected to one vnet. If you want a domain to have more than one vnet it needs more than one virtual interface - just like you need multiple real nics to have access to multiple lans. > 2) Can you run more than one vnet on the same bridge? A vnet is implemented by a vnet interface that does the multipoint tunneling for it. The vnet interface is connected to virtual interfaces via a bridge. The idea is to have one bridge per vnet. If you put more than one vnet interface on the same bridge I'm not sure whether it would work or not. Not something I've tried. If it did work it would be like bridging lans together via hub. > > ex. bridge=mgmt > vnetid=1 mac=aa:00:00:00:00:01 > vnetid=2 mac=aa:00:00:00:00:01 > > vnetid=1 mac=aa:00:00:00:00:02 > vnetid=3 mac=aa:00:00:00:00:02 > > vnetid=1 mac=aa:00:00:00:00:03 > > vnetid=3 mac=aa:00:00:00:00:04 > > domU1 mac=aa:00:00:00:00:01 bridge=mgmt > > domU2 mac=aa:00:00:00:00:02 bridge=mgmt > > domU3 mac=aa:00:00:00:00:03 bridge=mgmt > > domU4 mac=aa:00:00:00:00:04 bridge=mgmt > > all four hosts have an unique ip assigned from 192.168.1.0/24 > > domU1 can see domU2 and domU3 > > domU2 can see domU1 and domU4 > > dom3 can see domU1 > > dom4 can see domU2 > > > Will this work? I would try it out myself, but being that I can't > compile the code just yet, I thought I'd pick someone else's brain on > this while I work on the build issues. Not as it stands - see above. > > B. > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel Mike ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click