Device tap210i0 entered promiscuous mode

1

I have a Proxmox server that has been going offline a couple of times since a couple of weeks, when I added a second VM in it. Only the network seems affected until (remote) reboot.

I see these in the logs, maybe it’s related:

Jun 18 20:47:07 dal-node1 kernel: [   14.029390] device tap210i0 entered promiscuous mode
Jun 18 20:47:07 dal-node1 kernel: [   14.035468] vmbr0: port 1(tap210i0) entered blocking state
Jun 18 20:47:07 dal-node1 kernel: [   14.035469] vmbr0: port 1(tap210i0) entered disabled state
Jun 18 20:47:07 dal-node1 kernel: [   14.035556] vmbr0: port 1(tap210i0) entered blocking state
Jun 18 20:47:07 dal-node1 kernel: [   14.035557] vmbr0: port 1(tap210i0) entered forwarding state
Jun 18 20:47:11 dal-node1 kernel: [   17.606185] device tap211i0 entered promiscuous mode
Jun 18 20:47:11 dal-node1 kernel: [   17.612774] vmbr0: port 2(tap211i0) entered blocking state
Jun 18 20:47:11 dal-node1 kernel: [   17.612776] vmbr0: port 2(tap211i0) entered disabled state
Jun 18 20:47:11 dal-node1 kernel: [   17.612856] vmbr0: port 2(tap211i0) entered blocking state
Jun 18 20:47:11 dal-node1 kernel: [   17.612857] vmbr0: port 2(tap211i0) entered forwarding state

Network config:

iface eno1 inet static
	address x.x.x.209/24
	gateway x.x.x.1
	# dns-* options are implemented by the resolvconf package, if installed
	dns-nameservers 8.8.8.8
	dns-search theprovider.com
	post-up echo 1 > /proc/sys/net/ipv4/ip_forward
	post-up echo 1 > /proc/sys/net/ipv4/conf/eno1/proxy_arp

auto vmbr0
iface vmbr0 inet static
	address x.x.x.209
	netmask 255.255.255.0
	bridge-ports none
	bridge-stp off
	bridge-fd 0
	up ip route add x.x.x.210/32 dev vmbr0
	up ip route add x.x.x.211/32 dev vmbr0
	# more similar lines...
	up ip route add x.x.x.216/32 dev vmbr0

I’m using a similar config on another server with no problems at all.

Any ideas?

2

If you gave her the attention she needs she wouldn’t be feeling so promiscuous.

Thanks I’m here all night.

1 Like
3

What a hoe

1 Like