Re: br0: received packet on eth0 with own address as source address

[Sujata Verma <sujataverma3@xxxxxxxxx>]

Bernd,

We see this messages ,when there is a loop in the network. Basically, it means that the bridge is receiving same packets which it is sending.

Regards,
Sujata

---

From: "Lentes, Bernd" <bernd.lentes@xxxxxxxxxxxxxxxxxxxxx>
To: "Bridge ML (bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx)" <bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, August 30, 2013 10:49 PM
Subject: Re: br0: received packet on eth0 with own address as source address

Bernd wrote:
>
> Hi,
>
> i have a lot of the following messages in my /var/log/messages:
>
> Aug  7 10:37:32 pc60181 kernel: [2043056.982585] br0:
> received packet on eth0 with own address as source address
> [...]
>
> Messages appear for about 90 minutes and suddenly stopped.
>
> I have the following network configuration:
>
> pc60181:~ # ifconfig
> br0      Link encap:Ethernet  HWaddr 54:04:A6:94:F4:93
>          inet addr:10.35.23.36  Bcast:10.35.23.0  Mask:255.255.255.0
>          inet6 addr: fe80::5604:a6ff:fe94:f493/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:8087301 errors:0 dropped:196462
> overruns:0 frame:0
>          TX packets:1329744 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:480312835 (458.0 Mb)  TX bytes:1250573611
> (1192.6 Mb)
>
> eth0      Link encap:Ethernet  HWaddr 54:04:A6:94:F4:93
>          inet6 addr: fe80::5604:a6ff:fe94:f493/64 Scope:Link
>          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>          RX packets:424826060 errors:0 dropped:131484
> overruns:0 frame:0
>          TX packets:14092606 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:79356560631 (75680.3 Mb)  TX
> bytes:5338070565 (5090.7 Mb)
>          Interrupt:58 Base address:0x6000
>
> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          inet6 addr: ::1/128 Scope:Host
>          UP LOOPBACK RUNNING  MTU:16436  Metric:1
>          RX packets:3773045 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:3773045 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:0
>          RX bytes:3030507414 (2890.1 Mb)  TX
> bytes:3030507414 (2890.1 Mb)
>
> vnet0    Link encap:Ethernet  HWaddr FE:54:00:37:92:A0
>          inet6 addr: fe80::fc54:ff:fe37:92a0/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:81891 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:7394846 errors:0 dropped:0 overruns:6 carrier:0
>          collisions:0 txqueuelen:500
>          RX bytes:7477407 (7.1 Mb)  TX bytes:536978695 (512.1 Mb)
>
> pc60181:~ # brctl show
> bridge name    bridge id              STP enabled    interfaces
> br0            8000.5404a694f493      no              eth0
>                                                        vnet0
>
> The bridge is used to connect a KVM VM network adapter to the
> one of the host.
> Host is a SLES 11 SP2 64bit. Guest also.
>
> What is the reason for this message ? I can't remember if i
> had a loss of connectivity for that host/vm, because i
> realised the message some days after the error appeared.

Stop. I checked some emails and saw that the host was not accessible during this time.

>
> Any ideas ?
>
> I have now tcpdump running to see the exact packets if the
> error reappears.
>
>
> Bernd
>
>
>
>
>

I'm googleing for three days and found tons of these messages, but no clear reason/explaination. Any help would be really appreciated.


Beernd

Helmholtz Zentrum München
Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH)
Ingolstädter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir´in Bärbel Brumme-Bothe
Geschäftsführer: Prof. Dr. Günther Wess Dr. Nikolaus Blum Dr. Alfons Enhsen
Registergericht: Amtsgericht München HRB 6466
USt-IdNr: DE 129521671