Intermittent/broken networking

lividhen

New Member
Jun 20, 2025
2
0
1
Hello! I am having a very strange issue that I'm not quite sure how to solve. On my PVE host (clean install) I can access the internet and ping things on my local network as well, as is expected. I can also ping guests but it seems to be very lossy, losing the first 3-5 packets and then randomly losing them after that. Within 2 debian containers and 1 bazzite (fedora based distro) vm, I can sometimes (intermittently) ping things on my lan but I can't ping the gateway, anything on the internet (unless I leave it running 20+ minutes, then sometimes) or the proxmox host except for sometimes when I can ping the host for a few seconds. I can also ping the guest from devices on my lan with an occasional packet getting through. The longer I leave the vm/ct running the easier time it seems to have connecting to things but it is never fully consistent. DHCP doesn't seem to work on guests at all. I have tried using `ethtool -K eno1 tx off rx off tso off gso off gro off` from here which seemed to maybe help at first but after rebooting the host the issue came back, and I dont seem to be able to get it to work again. This is all being done on a supermicro x11ssl board which has an Intel i210 AT network controller with an i3-6100 cpu.

Proxmox /etc/network/interfaces:
Code:
auto lo

iface lo inet loopback


iface eno1 inet manual


iface eno2 inet manual


auto vmbr0

iface vmbr0 inet static

        address 192.168.1.42/24

        gateway 192.168.1.1

        bridge-ports eno1

        bridge-stp off

        bridge-fd 0


source /etc/network/interfaces.d/*

Output of ip a on proxmox:
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::1/128 scope host noprefixroute

       valid_lft forever preferred_lft forever

2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000

    link/ether 0c:c4:7a:e3:3f:b0 brd ff:ff:ff:ff:ff:ff

    altname enp3s0

3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

    link/ether 0c:c4:7a:e3:3f:b1 brd ff:ff:ff:ff:ff:ff

    altname enp4s0

4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000

    link/ether 0c:c4:7a:e3:3f:b0 brd ff:ff:ff:ff:ff:ff

    inet 192.168.1.42/24 scope global vmbr0

       valid_lft forever preferred_lft forever

    inet6 fe80::ec4:7aff:fee3:3fb0/64 scope link

       valid_lft forever preferred_lft forever

5: veth100i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000

    link/ether fe:19:e7:62:06:cb brd ff:ff:ff:ff:ff:ff link-netnsid 0

6: veth101i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000

    link/ether fe:13:8f:0d:a3:33 brd ff:ff:ff:ff:ff:ff link-netnsid 1

7: tap102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000

    link/ether 26:b1:c3:b3:6d:b3 brd ff:ff:ff:ff:ff:ff

Output of ip r on proxmox:
Code:
default via 192.168.1.1 dev vmbr0 proto kernel onlink

192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.42


Guest /etc/network/interfaces:
Code:
auto lo

iface lo inet loopback


auto eth0

iface eth0 inet static

        address 192.168.1.46/24

        gateway 192.168.1.1

Output of ip a on guest:
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

    inet 127.0.0.1/8 scope host lo

       valid_lft forever preferred_lft forever

2: eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000

    link/ether bc:24:11:6e:ee:0b brd ff:ff:ff:ff:ff:ff link-netnsid 0

    inet 192.168.1.46/24 brd 192.168.1.255 scope global eth0

       valid_lft forever preferred_lft forever

3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default

    link/ether 52:d4:29:86:53:e7 brd ff:ff:ff:ff:ff:ff

    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0

       valid_lft forever preferred_lft forever

Output of ip r on guest:
Code:
default via 192.168.1.1 dev eth0 onlink

172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown

192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.46

If there is any more information I can give or if my post didn't make sense please let me know.
 
Last edited:
VM conf:
Code:
agent: 1
boot: order=scsi0;net0
cores: 4
cpu: x86-64-v2-AES
memory: 12288
meta: creation-qemu=9.2.0,ctime=1750388376
name: bazzite
net0: virtio=BC:24:11:0E:E2:E3,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsi0: local-lvm:vm-102-disk-0,backup=0,iothread=1,size=100G
scsihw: virtio-scsi-single
smbios1: uuid=c78d481d-031c-4180-b432-0306155122da
sockets: 1
vmgenid: 1ed7376b-7d54-4002-8ef6-705a5d4bb6be

CT 1 conf:
Code:
arch: amd64
cores: 2
features: keyctl=1,nesting=1,fuse=1
hostname: docker
memory: 2048
nameserver: 9.9.9.9
net0: name=eth0,bridge=vmbr0,gw=192.168.1.1,hwaddr=BC:24:11:6E:EE:0B,ip=192.168.1.46/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-100-disk-0,size=4G
swap: 512
unprivileged: 1

CT 2 conf:
Code:
arch: amd64
cores: 4
features: keyctl=1,nesting=1,fuse=1
hostname: debian
memory: 6144
nameserver: 9.9.9.9
net0: name=eth0,bridge=vmbr0,gw=192.168.1.1,hwaddr=BC:24:11:6A:88:C5,ip=192.168.1.47/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-101-disk-0,size=35G
swap: 512
unprivileged: 1
 
Last edited:
Thank you for sharing the guest configurations. I do not see any issues with the configurations.

Do you have a DHCP server on your 192.168.1.0/24 network? If you do, what is the range?

The ping behaviour you describe could be duplicate IP addresses or MAC addresses on your network.

If you power off your guests (VMs and LXCs), can you still ping them?
 
  • Like
Reactions: UdoB