Errors on network interfaces

philled

Active Member
May 25, 2015
36
1
28
I have a pfSense router running as a VM on Proxmox 6.1.8. I've recently been getting internet connectivity issues which I originally thought may be my ISP. However, I've found these errors in /var/log/kern.log which look scary:

Apr 18 12:41:39 pve2 kernel: [ 20.057909] vmbr0: port 1(eno1) entered blocking state
Apr 18 12:41:39 pve2 kernel: [ 20.057911] vmbr0: port 1(eno1) entered disabled state
Apr 18 12:41:39 pve2 kernel: [ 20.057958] device eno1 entered promiscuous mode
Apr 18 12:41:39 pve2 kernel: [ 20.602832] vmbr1: port 1(enp1s0f0) entered blocking state
Apr 18 12:41:39 pve2 kernel: [ 20.602834] vmbr1: port 1(enp1s0f0) entered disabled state
Apr 18 12:41:39 pve2 kernel: [ 20.602894] device enp1s0f0 entered promiscuous mode
Apr 18 12:41:40 pve2 kernel: [ 20.980716] vmbr2: port 1(enp1s0f1) entered blocking state
Apr 18 12:41:40 pve2 kernel: [ 20.980717] vmbr2: port 1(enp1s0f1) entered disabled state
Apr 18 12:41:40 pve2 kernel: [ 20.980766] device enp1s0f1 entered promiscuous mode
Apr 18 12:41:40 pve2 kernel: [ 21.707654] bpfilter: Loaded bpfilter_umh pid 2144
Apr 18 12:41:42 pve2 kernel: [ 23.176924] e1000e: enp1s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Apr 18 12:41:42 pve2 kernel: [ 23.177072] vmbr2: port 1(enp1s0f1) entered blocking state
Apr 18 12:41:42 pve2 kernel: [ 23.177073] vmbr2: port 1(enp1s0f1) entered forwarding state
Apr 18 12:41:42 pve2 kernel: [ 23.177124] IPv6: ADDRCONF(NETDEV_CHANGE): vmbr2: link becomes ready
Apr 18 12:41:42 pve2 kernel: [ 23.856898] e1000e: enp1s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Apr 18 12:41:42 pve2 kernel: [ 23.857043] vmbr1: port 1(enp1s0f0) entered blocking state
Apr 18 12:41:42 pve2 kernel: [ 23.857045] vmbr1: port 1(enp1s0f0) entered forwarding state
Apr 18 12:41:42 pve2 kernel: [ 23.857101] IPv6: ADDRCONF(NETDEV_CHANGE): vmbr1: link becomes ready
Apr 18 12:41:43 pve2 kernel: [ 23.982087] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Apr 18 12:41:43 pve2 kernel: [ 23.982136] vmbr0: port 1(eno1) entered blocking state
Apr 18 12:41:43 pve2 kernel: [ 23.982137] vmbr0: port 1(eno1) entered forwarding state
Apr 18 12:41:43 pve2 kernel: [ 23.982215] IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready
Apr 18 12:41:53 pve2 kernel: [ 34.019724] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
Apr 18 12:41:53 pve2 kernel: [ 34.489304] device tap106i0 entered promiscuous mode
Apr 18 12:41:53 pve2 kernel: [ 34.496649] vmbr0: port 2(tap106i0) entered blocking state
Apr 18 12:41:53 pve2 kernel: [ 34.496651] vmbr0: port 2(tap106i0) entered disabled state
Apr 18 12:41:53 pve2 kernel: [ 34.496740] vmbr0: port 2(tap106i0) entered blocking state
Apr 18 12:41:53 pve2 kernel: [ 34.496742] vmbr0: port 2(tap106i0) entered forwarding state
Apr 18 12:41:54 pve2 kernel: [ 35.031526] device tap106i1 entered promiscuous mode
Apr 18 12:41:54 pve2 kernel: [ 35.038735] vmbr1: port 2(tap106i1) entered blocking state
Apr 18 12:41:54 pve2 kernel: [ 35.038737] vmbr1: port 2(tap106i1) entered disabled state
Apr 18 12:41:54 pve2 kernel: [ 35.038831] vmbr1: port 2(tap106i1) entered blocking state
Apr 18 12:41:54 pve2 kernel: [ 35.038832] vmbr1: port 2(tap106i1) entered forwarding state
Apr 18 12:41:54 pve2 kernel: [ 35.482556] device tap106i2 entered promiscuous mode
Apr 18 12:41:54 pve2 kernel: [ 35.489871] vmbr2: port 2(tap106i2) entered blocking state
Apr 18 12:41:54 pve2 kernel: [ 35.489873] vmbr2: port 2(tap106i2) entered disabled state
Apr 18 12:41:54 pve2 kernel: [ 35.489961] vmbr2: port 2(tap106i2) entered blocking state
Apr 18 12:41:54 pve2 kernel: [ 35.489962] vmbr2: port 2(tap106i2) entered forwarding state
Apr 18 12:41:59 pve2 kernel: [ 40.177117] device tap100i0 entered promiscuous mode
Apr 18 12:41:59 pve2 kernel: [ 40.184533] vmbr0: port 3(tap100i0) entered blocking state
Apr 18 12:41:59 pve2 kernel: [ 40.184535] vmbr0: port 3(tap100i0) entered disabled state
Apr 18 12:41:59 pve2 kernel: [ 40.184624] vmbr0: port 3(tap100i0) entered blocking state
Apr 18 12:41:59 pve2 kernel: [ 40.184625] vmbr0: port 3(tap100i0) entered forwarding state


I suspect these are the cause of my internet connection issues. Does anyone know what they indicate and what I need to do to fix it?

BTW the Proxmox server has 3 NICs and these are set up on the pfSense router: 1 for LAN, 1 for WAN connected directly to the modem, and 1 for DMZ.
 
The state changes can but don't have to be bad. They happen for example if you start a guest. Have you done anything special with your VMs while this happened?
 
hi guys,

i solved problem change to harddisk. (For entered disable state and blocking state)

i was using sata ssd

i changed nvme disk and solved.

i think sata not enough for 10 or 1 gigabit lan

sory for my bad english
 

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!