This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Communication between Domain0 and Domain1

To: Derek Glidden <dglidden@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Communication between Domain0 and Domain1
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Sun, 18 Jul 2004 20:09:21 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Sun, 18 Jul 2004 20:11:12 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Sun, 18 Jul 2004 14:43:46 EDT." <66DED5A5-D8EA-11D8-9A53-000A95DBAEDE@xxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> An alternative (and the way I prefer because of the bridge issues) is 
> to skip the bridging and just use your dom0 host as a firewall.  Assign 
> the dom0 vif an IP like, then assign the VM eth0 an IP like 
> and point to as the default route for the VM.  
> Create an ethernet alias on the dom0 host for whatever external IP you 
> wish to assign to the VM, and use iptables to NAT traffic to/from that 
> interface.  Everyone else on the network will see the VM as the 
> external IP you've assigned, but the dom0 host itself will use the 
> address to access the VM.  This is the way I've set up my 
> Xen dev box and it's working great for me.

I haven't had any problems with bridging, but I agree that the L3
routing solution may be better under some circumstances. 

It's a slight pain that the vifx.y interface in dom0 needs to be
given it's own an IP address, as it won't accept being operated
in 'pointopoint' mode. I suspect there's some ioctl we could add
to the backend driver that would enable this. Anyone know about

It would be good to have a 'vif-router' script to use as an
alternative to 'vif-bridge' for users wanting to operate a routed
configuration. If you've got something suitable we could check in
to the repo that would be great. I guess a modified 'network'
script would be required too.


This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
Xen-devel mailing list