PVE: vmbr0 enters/leaves promiscuous mode repeatedly...server eventually becomes unresponsive

[hive]

Hi Folks,
Does anyone know what might be going on? I'm seeing vmbr0 flipping into and out of promiscuous mode, until, eventually (< 1 hour), the machine becomes completely unresponsive (even from the console) and I have to power cycle/reset the machine.
Debugging is a bit challenging, since the server is in a cool.
What suggestions do you have on info to collect/possible root cause, so the next time I get remote hands to power cycle the machine, I can hopefully get to the bottom os this and resolve this issue?

Here is an example of what I am seeing on the console (before the server becomes unresponsive):

[11491.340751] device vmbro left promiscuous mode
[11492.045242] device vmbro entered promiscuous mode
[11495.352607] device vmbro left promiscuous mode
[11496.104780] device vmbro entered promiscuous mode
[11499.160518] device vmbro left promiscuous mode
[11499.824780] device vmbro entered promiscuous mode
[11503.060690] device vmbro left promiscuous mode
[11503.788211] device vmbro entered promiscuous mode
[11506.800454] device vmbro left promiscuous mode
[11507.562035] device vmbro entered promiscuous mode
[11510.496509] device vmbro left promiscuous mode
[11511.065265] device vmbro entered promiscuous mode
[11514.204406] device vmbro left promiscuous mode
[11514.793325] device vmbro entered promiscuous mode

What ideas you folks have on what to do to get to the bottom of this?

 

[ekzidua]

same situation here

[Sat Dec 23 13:03:03 2023] device eth0 entered promiscuous mode
[Sat Dec 23 13:03:14 2023] device eth0 left promiscuous mode
[Sat Dec 23 13:06:08 2023] device eth0 entered promiscuous mode
[Sat Dec 23 13:06:19 2023] device eth0 left promiscuous mode
[Sat Dec 23 13:07:01 2023] device eth0 entered promiscuous mode

:~# ethtool -k eno1 | grep offload
tcp-segmentation-offload: off
generic-segmentation-offload: off
generic-receive-offload: off
large-receive-offload: off [fixed]
rx-vlan-offload: on
tx-vlan-offload: on
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]
esp-hw-offload: off [fixed]
esp-tx-csum-hw-offload: off [fixed]
rx-udp_tunnel-port-offload: off [fixed]
tls-hw-tx-offload: off [fixed]
tls-hw-rx-offload: off [fixed]
macsec-hw-offload: off [fixed]
hsr-tag-ins-offload: off [fixed]
hsr-tag-rm-offload: off [fixed]
hsr-fwd-offload: off [fixed]
hsr-dup-offload: off [fixed]

:~# cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual
post-up /usr/sbin/ethtool -K $IFACE tso off gso off 2> /dev/null

auto enx00000000205d
iface enx00000000205d inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.0.11/24
gateway 192.168.0.1
bridge-ports eno1
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
#LAN

auto vmbr1
iface vmbr1 inet manual
bridge-ports enx00000000205d
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
#WAN

auto vmbr2
iface vmbr2 inet static
address 192.168.1.11/24
bridge-ports none
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
#DMZ

 

[news]

I see: vmbro but i shut be vmbr0.
A typo error?

 

[hive]

same situation here

[Sat Dec 23 13:03:03 2023] device eth0 entered promiscuous mode
[Sat Dec 23 13:03:14 2023] device eth0 left promiscuous mode
[Sat Dec 23 13:06:08 2023] device eth0 entered promiscuous mode
[Sat Dec 23 13:06:19 2023] device eth0 left promiscuous mode
[Sat Dec 23 13:07:01 2023] device eth0 entered promiscuous mode

It turned out that the root cause on my system was suricata (most likely a misconfiguration of suricata).
My workaround was to disable suricata (I am using crowdsec):

sudo systemctl stop suricata.service
sudo systemctl disable suricata.service