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

Re: [Xen-users] no bridge is shown by ifconfig on Xen Debian


  • To: Grant McWilliams <grantmasterflash@xxxxxxxxx>
  • From: chris <tknchris@xxxxxxxxx>
  • Date: Sat, 10 Apr 2010 22:39:05 -0400
  • Cc: linux-poweredge@xxxxxxxx, Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>, Tapas Mishra <mightydreams@xxxxxxxxx>
  • Delivery-date: Sat, 10 Apr 2010 19:40:21 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ltG+PyGh8+qjMKwA2JN4RvsOgVm/UJ5/R6AhEgWmjVV6lgcj25gc+mw9k5wUIuD3Ui lQdWZAm3xtilTYE3J3LvSArinYlt4bk3LIM2v4xEiYn3MOysGVJVCII7dUb069j36j50 aC9MLxqGE7YgtLePJSe0TAk7zPQjO0Wy7Deeo=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I agree with Grant, the mystery is solved. It is just that some of the
docs are a bit dated. Your bridge is working properly and your cfg
files should use the eth2 bridge rather than xenbr0.

- chris

On Sat, Apr 10, 2010 at 9:15 PM, Grant McWilliams
<grantmasterflash@xxxxxxxxx> wrote:
>
> On Sat, Apr 10, 2010 at 12:13 PM, Tapas Mishra <mightydreams@xxxxxxxxx>
> wrote:
>>
>> xenserver:~# brctl show
>> bridge name     bridge id               STP enabled     interfaces
>> eth2            8000.0026b9824238       no              peth2
>>                                                        vif1.0
>>                                                        vif2.0
>>                                                        vif3.0
>>                                                        vif4.0
>>
>>
>> It is showing eth2 that is what is my problem is I am running xen 3.2
>> and if I refer to that doc it should be xen-br0 since they are
>> mentioning that bridge name will be same as the interface name if it
>> is xen 3.3 or above.
>>
>
> But we solved the mystery by just looking right? As far as the bridge name
> being the same as your interface name it is - eth2. It looks like your
> physical interface comes up as eth2 for whatever reason then Xend renames it
> to peth2, sets up a bridge named eth2 and adds peth2 to it.
>
>  So what we see is that you have one bridge (eth2) and all interfaces real
> or virtual are on it. This means that those  VMs should be communicating on
> the real network like they're real machines. If you want to redirect
> connections from the public network you can have your router between you and
> the outside world port forward to the VMs and you're done. The VMs should
> already be able to connect to the internet.
>
> Grant McWilliams
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

_______________________________________________
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®.