From: Nicholas Lee <nic-lists@plumtree.co.nz>
To: Christian Wicke <xen.christian@safersignup.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Networking problems with debian packages
Date: Sat, 5 Mar 2005 22:19:36 +1300 [thread overview]
Message-ID: <20050305091936.GA21010@stateless> (raw)
In-Reply-To: <200503051012.30922.xen.christian@safersignup.com>
On Sat, Mar 05, 2005 at 10:12:30AM +0100, Christian Wicke wrote:
> * If I have a local network with free ip addresses in my subnet, then I assign
> those addresses to my domUs. The debian packages plus iproute work out of the
> box.
Yes, bridged network.
> * If I don't have free ip addresses in the subnet of eth0, I use local
> addresses for my domU. I can bridge the vif interfaces so that they the domUs
> can talk to each other, but eth0 must not be on the bridge. I need to set up
> masquerading and ip forwarding if domU wants to connect to the internet.
I suggest you create a second bridge interface for routed vs bridge
interfaces.
Nicholas
-------------------------------------------------------
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-03-05 9:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 11:13 Networking problems with debian packages Christian Wicke
2005-03-03 11:37 ` Leigh Brown
2005-03-03 12:58 ` Christian Wicke
2005-03-03 18:48 ` Nicholas Lee
2005-03-03 21:14 ` Christian Wicke
2005-03-04 21:15 ` Nicholas Lee
2005-03-05 9:12 ` Christian Wicke
2005-03-05 9:19 ` Nicholas Lee [this message]
2005-03-03 16:26 ` Christian Wicke
2005-03-03 17:44 ` Adam Heath
2005-03-04 16:16 ` B.G. Bruce
2005-03-03 14:45 ` Gerd Knorr
2005-03-04 21:22 ` Nicholas Lee
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=20050305091936.GA21010@stateless \
--to=nic-lists@plumtree.co.nz \
--cc=xen-devel@lists.sourceforge.net \
--cc=xen.christian@safersignup.com \
/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.