Device eno1 entered promiscuous mode automatically

Linyu

Active Member
Jun 14, 2019
43
2
28
24
Hi community,
I found abnormal network traffic on my proxmox host, and the kernel reported that the network device entered promiscuous mode and I could not disable it..

Code:
root@node-xz:~# grep -r 'promiscuous' /var/log/kern.log
Sep  5 08:22:49 node-xz kernel: [   12.537596] device eno1 entered promiscuous mode
Sep  5 08:23:04 node-xz kernel: [   27.014857] device tap100i0 entered promiscuous mode
Sep  5 08:27:15 node-xz kernel: [   12.303318] device eno1 entered promiscuous mode
Sep  5 08:27:31 node-xz kernel: [   27.573943] device tap100i0 entered promiscuous mode

The promiscuous mode start automatically and I could not disable it !

Code:
root@node-xz:~# ifconfig eno1 -promisc
root@node-xz:~# ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

And there is no promisc flag in ifconfig, and I've checked the kernel, nothing happend.

Code:
root@node-xz:~# grep -r 'promiscuous' /var/log/kern.log
Sep  5 08:22:49 node-xz kernel: [   12.537596] device eno1 entered promiscuous mode
Sep  5 08:23:04 node-xz kernel: [   27.014857] device tap100i0 entered promiscuous mode
Sep  5 08:27:15 node-xz kernel: [   12.303318] device eno1 entered promiscuous mode
Sep  5 08:27:31 node-xz kernel: [   27.573943] device tap100i0 entered promiscuous mode

Here is my network configuration.

Code:
source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

auto vmbr0
iface vmbr0 inet static
        address *.*.*.*
        netmask *.*.*.*
        gateway *.*.*.*
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet static
        address 192.168.1.1
        netmask 255.255.255.0
        bridge-ports none
        bridge-stp off
        bridge-fd 0
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward

PS: I've tried to reinstall the os to proxmox 6, nothing changed.
Can you help me? : (
 
This is default behavior. It's needed for VM traffic.
 
I have the same problem/error after some time all VMS freeze the only choice is to reboot the server
Sep 29 01:34:36 market kernel: [ 11.967305] device eno1 entered promiscuous mode

Sep 29 02:36:34 market kernel: [ 3729.925902] device tap100i0 entered promiscuous mode
Sep 29 02:36:34 market kernel: [ 3729.995402] device fwln100i0 entered promiscuous mode
Sep 29 02:36:34 market kernel: [ 3730.024609] device fwpr100p0 entered promiscuous mode
Sep 29 02:45:34 market kernel: [ 4270.198631] device enp129s0f0 entered promiscuous mode
Sep 29 03:12:48 market kernel: [ 5904.680368] device fwln100i0 left promiscuous mode
Sep 29 03:12:49 market kernel: [ 5904.740596] device fwpr100p0 left promiscuous mode
Sep 29 03:13:18 market kernel: [ 5934.227660] device tap100i0 entered promiscuous mode
keeps on going for few pages....
 
Last edited:

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!