WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xen-unstable networking

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen-unstable networking
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 27 Mar 2004 18:07:02 +0000
Cc: Chris Andrews <chris@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 27 Mar 2004 18:10:50 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Sat, 27 Mar 2004 17:10:11 GMT." <E1B7HJz-00065A-00@xxxxxxxxxxxxxxxxx>
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
> With this configuration, the packets will go out on the wire
> directly as you've told it that the whole 192.168.101.0/24 subnet
> is directly accessible from eth0
> 
> Try setting the ip addresses for domains >0 to
> e.g. 192.168.101.1/32 and then set the default route to go via
> gateway 192.168.101.254
> 
> I haven't tried this, but it should force all packets to go via
> domain 0 rather than out via the LAN. (You could set a gateway
> just for 192.168.101.0/24 if you wanted other packets to go on
> the LAN directly)
> 
> Ian

No, this won't work -- the gotcha is that Xen is forwarding packets
based on IP address, not MAC address. This approach will force the
destination MAC address of packets to DOM0's MAC address, but not teh
IP address. Unless the dest IP address belongs to another domain
running on the machine, the packets will still end up on the physical
wire. 

Also, 192.168.101.254 isn't in 192.168.101.1/32, so I'm not sure this
setup would even get that far --- how would the domain ARP for domain
0's MAC address?

 -- Keir


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>