new install eth0: received packet with own address as source

[Joe Baker]

I have been seeing this message on a Dell R610 with it's broadcom 4 port ethernet card (BCM5709 ).

I experienced about 26 seconds of stalls of ssh sessions going into the server from my laptop.

I've observed that that I can have a screen session with pings running continually during the stalled ssh session. So oddly, it doesn't seem like the server is totally disconnected. Maybe this is a switch problem.

I installed a new Ethernet card and it seemed to work quite stable for about 20 minutes, but then I had one session where the inbound ssh session froze up. Well, I did hear that there was a packet storm on the network about 3 weeks ago and I don't think that the core network switch was rebooted after that , so I had it rebooted this evening and I have not seen any problems since two hours ago. The packet storm was identified on some extended parts of the network serviced by smaller switches where there was an accidental loop in the wiring. the packet storm came up after a power failure.

I'm posting this in hopes that the information will be helpful to others searching for these unusual circumstances.

 

[apmuthu]

Since last week I am receiving this error

eth0: received packet with own address as source​

on a PVE 3.4 machine.

# pveversion -v
proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)
pve-kernel-2.6.32-37-pve: 2.6.32-147
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-31
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1