WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Bridge Setup problem in domU!

To: "Jan Muhammad" <janmuhd@xxxxxxxxx>
Subject: Re: [Xen-users] Bridge Setup problem in domU!
From: "Mark Hurenkamp" <mark.hurenkamp@xxxxxxxxx>
Date: Mon, 15 Feb 2010 17:50:46 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 15 Feb 2010 08:52:04 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <546230.56463.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <546230.56463.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.18
Hi Jan,


> Either I disable or enable DHCP option in config file still the error
> message is same (as follow).
> Although both dom0 and domU boot okay, except for a problem with bridge
> problem. The network bridge is never setup when the
> server is rebooted.  I have to shutdown domU, and then run
>
> ./network-bridge stop
> ./network-bridge start

I'm using a similar setup, running a Ubuntu Karmic dom0, and several
Debian/Ubuntu domU machines.

But I've completely stopped using the network-bridge scripts, and now
setup the bridge from my /etc/network/interfaces config file, which avoids
the whole problem of transfering IP, and renaming eth device completely.

Here's an example for setting up a bridge using Debian/Ubuntu:

auto br0
iface br0 inet static
        address 192.168.1.101
        network 192.168.1.0
        netmask 255.255.255.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        bridge_ports eth0

This has worked fine for me ever since the first xen-3.0 days ;-)


Regards,

Mark.



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