Search results

turns out it was a bad switch on my network.. I isolated the issue to that one switch and even when I disable all the ports I was still getting the issue. I disable the switch and the issue went away.. I have now replaced the switch.. Now that was something I have never expected the issue to be.

it was defiantly something on my network, I had a massive power outage this weekend, and when I got everything back up and running the errors went away, for now.. I am going to keep an eye on it to see if it happens again. And isolate it from there.

I looked through the arp on the switches and couldn't find a duplicate. I got this on 2 computers and 3 separate NICs.. something must be up on my network, I have it unplugged, I'll have to isolate it more on Monday.

I installed onto another box and after a bit I got the same issue.. I changed the IP and still have the same issue. reset the router, firewall and switches and still got the same issue.. turned off IPV6 rebooted and still get proxmox kernel: eth0: received packet with own address as source...

eth0 doesn't have an IP. When I get bac to work I will check /etc/network/interface, I also am going to try another box to see if it that is the cause.

I just installed a new instance of proxmox. it worked for a bit now I am getting a flood of proxmox kernel: eth0: received packet with own address as source in the syslog, making the server unusable. I can no longer SSH,ping or use the web interface on the box. I replaced the network card...