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

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



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

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.