From: "Daniel P. Berrange" <berrange@redhat.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] example and default IP addresses
Date: Fri, 18 Jan 2008 03:53:59 +0000 [thread overview]
Message-ID: <20080118035359.GB23440@redhat.com> (raw)
In-Reply-To: <20080117202701250.00000001968@djm-pc>
On Thu, Jan 17, 2008 at 08:27:01PM -0700, Dan Magenheimer wrote:
> > On Thu, Jan 17, 2008 at 03:35:02PM +0000, Ian Jackson wrote:
> > > Dan Magenheimer writes ("RE: [Xen-devel] [PATCH] example
> > and default IP addresses"):
> > > > In the patch to network-nat, I see that you are replacing
> > the 10.0.0.0/16
> > > > usage with 192.0.2.0/24. Actually, vif-nat has a dependency on it
> > > > being 10.0.0.0/8(!), at least if more than 256 domains
> > are launched (not
> > > > necessarily simultaneously, just sequentially created and
> > destroyed).
> > > > In vif-nat ip_from_dom, IP's are created as 10.x.y.z for
> > vifw.z, where
> > > > x*256+y==w.
> > >
> > > Firstly, I think it's important to note that network-nat and vif-nat
> > > are pretty ropey. Anyone who is using them will almost
> > certainly have
> > > had to adjust them to local conditions anyway. For example, these
> > > scripts attempt to find and edit your local dhcp server
> > configuration
> > > file !
> >
> > FYI, for anyone using libvirt we recommend only using network-bridge
> > and vif-bridge. libvirt then provides a 'virtual network' capability
> > which allows you to define multiple local networks either completely
> > isolated from the physical network, or connected via NAT.
> > This effectively
> > provides same functionality as vif-nat/network-nat, but
> > without requiring
> > the admin to modify shell scripts.
>
> Hi Dan --
>
> Does this handle DHCP as well? If so, can you provide a pointer to more
> information?
Yes, it runs a 'dnsmasq' daemon per virtual network to provide DNS and
DHCP services. Each virtual network is setup as a bridge device, so you
can have many on a single machine, each with independant DHCP services
The original design doc is
http://www.gnome.org/~markmc/virtual-networking.html
And UI screenshots are
http://virt-manager.org/screenshots/networking.html
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2008-01-18 3:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 15:12 [PATCH] example and default IP addresses Ian Jackson
2008-01-16 17:53 ` Dan Magenheimer
2008-01-17 15:35 ` Ian Jackson
2008-01-17 16:03 ` Daniel P. Berrange
2008-01-18 3:27 ` Dan Magenheimer
2008-01-18 3:53 ` Daniel P. Berrange [this message]
2008-01-18 1:52 ` Dan Magenheimer
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=20080118035359.GB23440@redhat.com \
--to=berrange@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=xen-devel@lists.xensource.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.