Re: [Xen-users] bridge with IP address, "received packet with own address as source address"

[Jaroslaw Zdrzalek <jz@xxxxxxxxxx>]

Am Mittwoch 08 November 2006 09:05 schrieb Ulrich Windl:
> Hi,
> 
> I've set up identical (what I think) machines using SLES 10 x86_64, but a new 
> one 
> of those is saying frequently in /var/log/messages:
> kernel: bond0: received packet with  own address as source address

First of all, you dont have to configure an ip for the bridge,
it is sufficient to configure a single interface (in your case bond0)
inside of the bridge.

What kind of bonding are you using (failover,trunk)?
Are both eth0 and eth1 bounded together?
The output of the "ifconfig" and "ip r" would be of interest.


cheers
Jaroslaw

> 
> A short summary of ifconfig looks like this:
> bond0     Link encap:Ethernet  HWaddr 00:14:4F:2A:12:9C
>           inet addr:132.199.176.78  Bcast:132.199.255.255  Mask:255.255.0.0
> eth0      Link encap:Ethernet  HWaddr 00:14:4F:2A:12:9C
>           inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link
> eth2      Link encap:Ethernet  HWaddr 00:14:4F:2A:12:9C
>           inet6 addr: fe80::214:4fff:fe2a:129c/64 Scope:Link
> vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
> xenbr0    Link encap:Ethernet  HWaddr 00:14:4F:2A:12:9C
>           inet addr:132.199.176.78  Bcast:132.199.255.255  Mask:255.255.0.0
>           inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> 
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.00144f2a129c       no              vif0.0
>                                                         bond0
> 
> On a machine where the problem is absent, brctl looks like this:
> # brctl show
> bridge name     bridge id               STP enabled     interfaces
> xenbr0          8000.feffffffffff       no              vif0.0
>                                                         peth0
>                                                         vif13.0
>                                                         vif12.0
> 
> 
> Related messages during boot:
> kernel: Bridge firewalling registered
> kernel: device vif0.0 entered promiscuous mode
> kernel: xenbr0: port 1(vif0.0) entering learning state
> kernel: xenbr0: topology change detected, propagating
> kernel: xenbr0: port 1(vif0.0) entering forwarding state
> kernel: device eth0 entered promiscuous mode
> kernel: device eth2 entered promiscuous mode
> kernel: device bond0 entered promiscuous mode
> ifup:     xenbr0
> ifup:               No configuration found for xenbr0
> kernel: xenbr0: port 2(bond0) entering learning state
> kernel: xenbr0: topology change detected, propagating
> kernel: xenbr0: port 2(bond0) entering forwarding state
> 
> The following was a bad idea: it killed networking:
> # ip addr del 132.199.176.78 dev xenbr0
> 
> Any insights?
> 
> Regards,
> Ulrich
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 

Mit freundlichen Grüßen
Jaroslaw Zdrzalek
-- 
-----------------------------------------------------------------
Dipl.-Ing. (FH) Jaroslaw Zdrzalek | e-mail jz@xxxxxxxxxx
Netzwerke und Sicherheit          | web    www.silpion.de
Silpion IT-Solutions GmbH         | tel    +49 (40) 39 99 76 54 
Brandshofer Deich 48              | fax    +49 (40) 39 99 76 40
20539 Hamburg                     | mobil  +49 (178) 39 99 76 3 
-----------------------------------------------------------------

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