Re: [Xen-users] Xen in a routed network environment?

[Andy Smith <andy@xxxxxxxxxxxxxx>]

On Wed, Jan 25, 2006 at 03:11:19PM +0000, Andy Smith wrote:
> On Wed, Jan 25, 2006 at 01:25:25AM +0100, Ralph Passgang wrote:
> > As you would configure it for every normal/physical server. Your router has 
> > to 
> > route traffic for this /29 to the same network interface as for the /24 you 
> > are already using right now. xen (in bridge mode) is just like having more 
> > then one realserver connected to one of your switchports (by using an 
> > additional switch/hub or whatever). I would suggest that you bind one ip 
> > out 
> > of the /29 on the router, and one other ip out of the /29 on your domU. The 
> > domU now only has to be configured to use the ip and the correct netmask + 
> > your router's ip (the one from the new /29 net) as default gateway. It 
> > doesn't need to know about your already existing /24 network, that there is 
> > a 
> > bridge between the domU and the router or something else.
> 
> Hi Ralph, thanks for your reply.
> 
> The above is what I thought but I can't seem to get it to work.

Right, I have now got it to work by manually adding an IP address
and switching routes around.  Is there something obvious I have
missed that enables this to work by itself after reboot?

> Here's what I have in dom0 immediately after booting with xend
> started and one domU running:
> 
> $ ip -4 addr
> 1: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>     inet 217.147.82.214/24 brd 217.147.82.255 scope global eth0
>     inet 217.147.93.65/29 brd 217.147.93.255 scope global eth0:1
> 2: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>     inet 127.0.0.1/8 scope host lo
> 4: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop
>     inet 217.147.82.214/24 brd 217.147.82.255 scope global veth0
> $ brctl show
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.feffffffffff       no              vif1.0
> $ ip ro
> 217.147.93.64/29 dev eth0  proto kernel  scope link  src 217.147.93.65
> 217.147.82.0/24 dev eth0  proto kernel  scope link  src 217.147.82.214
> default via 217.147.82.1 dev eth0

And here's what I have to do to make it work:

# ip addr add 217.147.93.65 dev xenbr0
# ip route del 217.147.93.64/29
# ip route add 217.147.93.64/29 dev xenbr0

Is there a more elegant way to make this Just Work?

Thanks,
Andy

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users