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] Attaching a bond to a bridge

To: <xen-users@xxxxxxxxxxxxxxxxxxx>, <jensampol@xxxxxxxx>
Subject: Re: [Xen-users] Attaching a bond to a bridge
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Tue, 29 Jul 2008 13:04:46 -0600
Cc:
Delivery-date: Tue, 29 Jul 2008 12:05:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

You need to do one of two things:

1) Remove the IP information from bond0 from your Linux distro (/etc/sysconfig/network-scripts/ifcfg-bond0).  Instead of "static" or "dhcp" use "none" for the address type.  You should then be able to use ifup bond0 to bring the interface up IP-free.

2) Instead of doing ifup bond0 use "ifconfig bond0 up" which should bring it up without trying to apply any of the information from the /etc/sysconfig... files.


-Nick

>>> On Tue, Jul 29, 2008 at  7:57 AM, Jens Ahrens <jensampol@xxxxxxxx> wrote:

Hi everybody,

I'm having a little bit of trouble with a non-standard (xen) bridge-setup.
I'm using FedoraCore7 and xen3.1.2.
The topology is as follows:

----------------------
|                DOM0|
|  ______________    |
|  | xen-pvm DomU|   |
|  --------------    |
|       |            |
|  ____________      |
|  | bridge b0 |     |
|  -------------     |
|       |            |
|  ____________      |
|  | bond0     |     |
|  -------------     |
|   |         |      |
|  ____      ____    |
| |eth0|    |eth1|   |
| ------    ------   |
|   |          |     |
----------------------
    |          |


Doing the following:
-----------------------
1)  brctl addbr b0
2)  brctl stp b0 off
3)  brctl setfd b0 0
4)  ip addr add 192.168.xx.xx brd 192.168.xx.255 scope global dev b0
5)  ifdown bond0
6)  ip link set bond0 down
7)  ip addr flush bond0
8)  ip link set bond0 up
9)  ifup bond0
10) brctl addif b0 bond0
11) ip link set b0 up
-----------------------
I end up with both bond0 and b0 having the same IP. If I leave out 9) I can't add bond0 to the bridge


What I usually do when setting up a bridge for a single NIC is the following:
----------------------
|                DOM0|
|  ______________    |
|  | xen-pvm DomU|   |
|  --------------    |
|       |            |
|  ______________    |
|  | bridge eth0 |   |
|  ---------------   |
|       |            |
|      _____         |
|     |peth0|        |
|     -------        |
|        |           |
----------------------
         |

1)  brctl addbr tmpbridge
2)  brctl stp tmpbridge off
3)  brctl setfd tmpbridge 0
4)  ip addr add 192.168.xx.xx brd 192.168.xx.255 scope global dev tmpbridge
5)  ifdown eth0
6)  ip link set eth0 name peth0
7)  ip link set tmpbridge name eth0
8)  ip link set peth0 down
9)  ip addr flush peth0
10) ip link set peth0 up
11) brctl addif eth0 peth0
12) ip link set peth0 up
13) ifup eth0

This works fine - the bridge eth0 gets the ip and peth0 remains without ip.

Any idea what I'm doing wrong?

Thanks and cheers,
Jens




      __________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com



This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>