> 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?
Thanks,
Dan
P.S. With the patch I posted yesterday, the admin doesn't have to modify
shell scripts for vif-nat and network-nat though admittedly the scripts
modify them directly which is probably OK if dom0 is not otherwise used
as a dhcp server.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home