All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derrik Pates <demon@devrandom.net>
To: Andrew Theurer <habanero@us.ibm.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: network advice needed
Date: Fri, 14 Jan 2005 15:15:42 -0500	[thread overview]
Message-ID: <41E8286E.8040906@devrandom.net> (raw)
In-Reply-To: <200501141040.11583.habanero@us.ibm.com>

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@devrandom.net


-------------------------------------------------------
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

  reply	other threads:[~2005-01-14 20:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 16:40 network advice needed Andrew Theurer
2005-01-14 20:15 ` Derrik Pates [this message]
2005-01-14 23:10   ` Andrew Theurer

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=41E8286E.8040906@devrandom.net \
    --to=demon@devrandom.net \
    --cc=habanero@us.ibm.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.