[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] network-bridge breaks networking when eth0:1 is added


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
  • Date: Mon, 27 Apr 2009 08:11:00 +0700
  • Delivery-date: Sun, 26 Apr 2009 18:11:42 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On Mon, Apr 27, 2009 at 7:27 AM, Kai Schaetzl <maillists@xxxxxxxxxxxxx> wrote:
> Kai Schaetzl wrote on Mon, 27 Apr 2009 01:47:07 +0200:
>
>> Which is rather weird, isn't it?
>
> Ok, the reason for this is simple. It seems that once the bridge is up a
> xend restart does not restart the network-bridge script. If I run the
> network-bridge script manually it breaks eth0 each time, not just the
> first time. It even breaks it with "network-bridge stop".

For non-standard networking setup (like the one where you have eth0:1)
it'd be much easier if you let the OS handle the bridge and have
something like (network-script /bin/true) on xend.sxp. So for example
you can have these files

/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-xenbr0
/etc/sysconfig/network-scripts/ifcfg-xenbr0:1

which would create the bridge xenbr0 with eth0 as physical device and
create a virtual interface on xenbr0:1 where you can assign a second
IP address.

An advantage of such approach is that you don't have to depend on xend
for network setup. You can restart xend anytime you want and
networking would still be OK.

Let me know if you need more detail on this setup (like what those
file's contents look like).

Regards,

Fajar

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.