Martian Destination

ducs4rs

Member
Apr 13, 2021
32
5
13
66
I am getting flooded with: IPv4: martian destination 0.0.0.0 from 192.168.1.1, dev ens2f1v0

I am using SR-IOV on a an intel quad port i350 nic. ens2f1v0 is a passthrough to an LXC container. This nic is 5:10.1

root@pveprod:/etc/pve/lxc# ip -br a lo UNKNOWN 127.0.0.1/8 ::1/128 ens2f0 UP ens2f1 UP fe80::a236:9fff:fe8c:d0bd/64 ens2f2 UP fe80::a236:9fff:fe8c:d0be/64 enp7s0 DOWN enp8s0 DOWN ens2f2v0 DOWN ens2f2v2 DOWN ens2f1v2 DOWN ens2f2v3 DOWN ens2f1v3 DOWN ens2f2v4 DOWN ens2f2v5 DOWN ens2f2v6 DOWN ens2f1v6 DOWN vmbr0 UP 192.168.1.31/24 fe80::a236:9fff:fe8c:d0bc/64 veth111i0@if2 UP fwbr111i0 UP fwpr111p0@fwln111i0 UP fwln111i0@fwpr111p0 UP

root@pveprod:/etc/pve/lxc# ~/vflist.sh Virtual Functions on Intel Corporation I350 Gigabit Network Connection. (ens2f1): PCI BDF Interface ======= ========= 0000:05:10.1 0000:05:10.5 0000:05:11.1 ens2f1v2 0000:05:11.5 ens2f1v3 0000:05:12.1 0000:05:12.5 0000:05:13.1 ens2f1v6 Virtual Functions on Intel Corporation I350 Gigabit Network Connection. (ens2f2): PCI BDF Interface ======= ========= 0000:05:10.2 ens2f2v0 0000:05:10.6 0000:05:11.2 ens2f2v2 0000:05:11.6 ens2f2v3 0000:05:12.2 ens2f2v4 0000:05:12.6 ens2f2v5 0000:05:13.2 ens2f2v6

See the config for the container below

root@pveprod:/etc/pve/lxc# cat 102.conf arch: amd64 cores: 1 features: nesting=1 hostname: nas1 memory: 512 mp0: <source>,mp=<destination> mp1: <source>,mp=<destination> mp2: <source>,mp=<destination> mp3: <source>,mp=<destination> mp4: <source>,mp=<destination> mp5: <source>,mp=<destination> mp6: <source>,mp=<destination> mp7: <source>,mp=<destination> nameserver: ns1, ns2 onboot: 1 ostype: debian rootfs: vm_images:102/vm-102-disk-0.raw,size=8G searchdomain: foo.net startup: order=3 swap: 512 unprivileged: 1 lxc.net.0.type: phys lxc.net.0.flags: up lxc.net.0.link: ens2f1v0 lxc.net.0.mtu: 1500 lxc.net.0.hwaddr: e2:ba:7c:07:f0:6d

when I power down the LXC container the martian errors stop. Any suggestions on how to fix this? Why is it only the LXC with passthrough that gets this error from the kernel?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!