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] howto re-create XEN network bridge?

To: Rudi Ahlers <Rudi@xxxxxxxxxxx>
Subject: Re: [Xen-users] howto re-create XEN network bridge?
From: Rudi Ahlers <Rudi@xxxxxxxxxxx>
Date: Fri, 6 Nov 2009 22:08:03 +0200
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 06 Nov 2009 12:09:03 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding; bh=xq0icB4ESrxpymLyms2Mm+ATX/iezRE9C9UfssDTw6Q=; b=rcvNKSIZVOZG/6k1Fqmi2JM6bsU6J0m7IjRxmv8YY1UI6sC4tnQwWsXM/3+QbWkloE 7PM5UtX1KoDITCjMgz+2JnKBn8KKI9Tc2P87FT1sn4J+AGhIJ4V3hteWCpjR3NmfT8C8 L6tgbucVs23p8s964bbrfhtfyjqm4x2KdFhac=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=m5QQYp6o7U/HqkhqiC9eeUm3DeexYyZg/EZiBKnyaNneqk28plepa8unSZcW0TnNTQ +l7THYC/lPL/BShNE53T84OAZe/c09frAfi2XGVcKCJdJm0FAFrgKBNRh5CSWqdvxq6p Em3dD5StU1hV8dynfHZR9eFOum5boHwsS1Ra0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <695200da0911061028s16493f7o3cca0ca8885bc3de@xxxxxxxxxxxxxx>
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: <695200da0911051558k550f57f4p9d45c718031c925e@xxxxxxxxxxxxxx> <7207d96f0911060148t170a2879r5ffe1f7bc4bc7d46@xxxxxxxxxxxxxx> <695200da0911060225g3c5eebep7f4bba0c336e6bae@xxxxxxxxxxxxxx> <7207d96f0911060238t4e37a845ybd72133e54e88967@xxxxxxxxxxxxxx> <695200da0911060250t5db5f7bcu272063af65c3e03f@xxxxxxxxxxxxxx> <7207d96f0911060259u276087e7n23abd38b0fb5c177@xxxxxxxxxxxxxx> <695200da0911060819k28ef9499y8213618bf15fc096@xxxxxxxxxxxxxx> <695200da0911061028s16493f7o3cca0ca8885bc3de@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Nov 6, 2009 at 8:28 PM, Rudi Ahlers <Rudi@xxxxxxxxxxx> wrote:
> On Fri, Nov 6, 2009 at 6:19 PM, Rudi Ahlers <Rudi@xxxxxxxxxxx> wrote:
>> On Fri, Nov 6, 2009 at 12:59 PM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
>>> On Fri, Nov 6, 2009 at 5:50 PM, Rudi Ahlers <Rudi@xxxxxxxxxxx> wrote:
>>>
>>>> Here's the output of brctl show:
>>>>
>>>>
>>>> root@zaxen01:[~]$ brctl show
>>>> bridge name     bridge id               STP enabled     interfaces
>>>> xenbr0          8000.feffffffffff       no              vifpict0
>>>>                                                        vifandr0
>>>>                                                        vifzafe0
>>>>                                                        vifserv0
>>>>                                                        vifraft0
>>>>                                                        vifplut0
>>>>                                                        viferis0
>>>>                                                        vifbyra0
>>>>                                                        vifanim0
>>>>                                                        vifacti0
>>>>                                                        peth0
>>>>                                                        vif0.0
>>>>
>>>
>>> You can try by sniffing packets on uplink physical interface (should
>>> be peth0 in your case). Test with simple packets (like ping) and snoop
>>> it with tcpdump (something like "tcpdump -n -i peth0 icmp"). That
>>> would at least tell you whether packets can get to physical interface
>>> or not.
>>>
>>> If the traffic is there but somehow you still have problems, the
>>> source of problem might be elsewhere and not in your bridge setup.
>>> Might be switch blocking ports with many MACs, or router caching old
>>> MAC addresses.
>>>
>>> --
>>> Fajar
>>>
>>> _______________________________________________
>>

Are there any limits on the amount of network interfaces one can setup on XEN?

I'm really at whit's end with this problem and don't know how to fix it.


-- 
Kind Regards
Rudi Ahlers
CEO, SoftDux Hosting
Web: http://www.SoftDux.com
Office: 087 805 9573
Cell: 082 554 7532

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