From: Mike Wray <mike.wray@hpl.hp.com>
To: bgb@nt-nv.com
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: Other additional vnet questions
Date: Thu, 10 Feb 2005 10:22:18 +0000 [thread overview]
Message-ID: <420B35DA.2080705@hpl.hp.com> (raw)
In-Reply-To: <1107965719.9884.237.camel@master.vms.security>
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
next prev parent reply other threads:[~2005-02-10 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 16:15 Other additional vnet questions B.G. Bruce
2005-02-10 10:22 ` Mike Wray [this message]
2005-02-10 12:38 ` B.G. Bruce
2005-02-10 13:21 ` Mike Wray
2005-02-10 14:39 ` B.G. Bruce
2005-02-10 16:55 ` B.G. Bruce
2005-02-11 23:31 ` Felipe Alfaro Solana
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=420B35DA.2080705@hpl.hp.com \
--to=mike.wray@hpl.hp.com \
--cc=bgb@nt-nv.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.