On Mon, Nov 27, 2006 at 10:44:17PM +0000, Pete McEvoy wrote:
> On Tue, Nov 28, 2006 at 08:29:54AM +1100, Matthew Palmer wrote:
> > So instead of allocating 10.0/16 addresses to your domUs, you just allocate
> > public IPs to your domUs.
> >
> > It might help to think of the bridge as a regular Ethernet switch, and each
> > of the machines (dom0 and domU) as a separate physical machine. Then you
> > just configure each machine as you would normally, and leave the bridge to
> > play Ethernet games in the middle. Using that mental model has never
> > steered me wrong yet.
>
> Thats a nice analogy, thanks.
>
> Would it be a reasonable facsimile of routable public ip addressing if I
> were to add an interface on a spare box I have with the gateway address
> in the datacentre, configure my xen hosts with the public ip addresses
> provided, and ensure they can communicate with each other on my internal
> network?
Yes.
> If not, can anyone confirm the following is what I need to do to move
> from my existing bridge setup using rfc1918 addresses to public routable
> ips:
>
> Change
> (network-script network-bridge)
> (vif-script vif-bridge)
>
> to
>
> (network-script network-route)
> (vif-script vif-route)
>
> in xend-config.sxp
Unless you're planning on doing the routing for your IP space on your dom0,
I don't think you want to do this. All of my setups have used an external
border router, and all of the domUs and dom0s (and other random machines)
have all been on the same ethernet segment. YMMV, though, depending on what
your provider plans on doing.
- Matt
--
I told [my daughter] that if I see her digging a hole that she might not be
able to crawl out of, my job isn't to stand back and say "That's a *real*
nice hole you're digging there".
-- Paul Tomblin, ASR
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home