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] "received packet with own address as source address"

To: tim.post@xxxxxxxxxxxxxxx
Subject: Re: [Xen-users] "received packet with own address as source address"
From: Tiago Cruz <tiagocruz@xxxxxxxxx>
Date: Mon, 30 Oct 2006 09:49:07 -0300
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 30 Oct 2006 04:49:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1162049814.3331.50.camel@tower>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1161985633.6895.4.camel@localhost> <1162049814.3331.50.camel@tower>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello Tim,

On Sat, 2006-10-28 at 23:36 +0800, Tim Post wrote:
> Can you post a copy of your bridge config? Looks like you have a bridge
> porting multiple nics and something went wrong. 

I'm getting one strange problem with FC5 running on XEN 3.0.3 x64, and I
suspect of my bridge configuration (I never did this before on fedora):

File /etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
TYPE=Ethernet
BRIDGE=xenbr0
ONBOOT=yes

File /etcsysconfig/network-scripts/ifcfg-xenbr0:
DEVICE=xenbr0
TYPE=BRIDGE
BOOTPROTO=dhcp
ONBOOT=yes


> Is STP enabled on any bridges?

No :)

# btctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.00137255e4c6       no              eth0
                                                        peth0
                                                        vif0.0

The problem start when I 'up' the xenbr0 interface... :-(

Thanks a lot!


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