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] network advice needed

To: Andrew Theurer <habanero@xxxxxxxxxx>
Subject: Re: [Xen-devel] network advice needed
From: Derrik Pates <demon@xxxxxxxxxxxxx>
Date: Fri, 14 Jan 2005 15:15:42 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 14 Jan 2005 21:34:34 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <200501141040.11583.habanero@xxxxxxxxxx>
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>
References: <200501141040.11583.habanero@xxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.9 (X11/20041124)
Andrew Theurer wrote:
Newbie Xen network advice needed. I'd like to do the following: Have domain0 masqerade all other domains (on that system) through the physical ethernet adapter in domain0. I'd like all of the other domains to have an IP addresses in 192.168.0.0/24. Domain0 will also dhcp serve IP's to the other domains. I want to do this, so I can dynamically create as many domains as I need without worrying about IP address assignment headaches.

As each domain has its own independent interface(s), you'd either (a) have to assign each individual interface its own /30, and dish out a specific DHCP IP for each one, or bridge them all together, and treat it as one big network.

doamin0: has my physical network adapter with my static IP address, and an ethernet bridge which has IP address of 192.168.0.1.

Makes sense.

domain[1-N]: has vifN.0, with IP address in subnet 192.168.0.0/24

Some iptables setup to MASQ from dev br0 and out eth0.

The main thing I see that needs chaning is simply not move domain0's eth0 IP address to the bridge, but assign it 192.168.0.1. Is that correct?

Yes, you should be able to hack the /etc/xen/scripts/network script to just not try to claim eth0's IP and not enslave it to the bridge device. It shouldn't be a huge change, mostly just commenting/removing things. Then just set up dhcpd and an iptables ruleset pretty much as you'd expect on a real network.

--
Derrik Pates
demon@xxxxxxxxxxxxx


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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