LXC DHCP Server restarts network devices ?

CvH

Member
Oct 16, 2020
25
4
23
Germany
Hi, we see this kind of problems since at least Proxmox 6.4.
We have a working isc-dhcp server at a unprivileged ubuntu container. The isc is restarted frequently (several times a day) due changes at dhcp.
Every time the server is restarted (due changes at the config), or the lxc itself is restarted the dhcp server is not available + everything that is located at the same physical proxmox host for at least 30sec.

At the container itself nothing strange could be observed looks pretty normal, but at the dmesg from the host proxmox you can see that it restarts? the network interfaces for some reason.
Is this something known or maybe a red hering and the real problem is something else ?
The problem is reproduce able at every proxmox host.

Code:
[Mon Nov 29 12:17:08 2021] fwbr163i0: port 1(fwln163i0) entered blocking state
[Mon Nov 29 12:17:08 2021] fwbr163i0: port 1(fwln163i0) entered disabled state
[Mon Nov 29 12:17:08 2021] device fwln163i0 entered promiscuous mode
[Mon Nov 29 12:17:08 2021] fwbr163i0: port 1(fwln163i0) entered blocking state
[Mon Nov 29 12:17:08 2021] fwbr163i0: port 1(fwln163i0) entered forwarding state
[Mon Nov 29 12:17:08 2021] vmbr1: port 18(fwpr163p0) entered blocking state
[Mon Nov 29 12:17:08 2021] vmbr1: port 18(fwpr163p0) entered disabled state
[Mon Nov 29 12:17:08 2021] device fwpr163p0 entered promiscuous mode
[Mon Nov 29 12:17:08 2021] vmbr1: port 18(fwpr163p0) entered blocking state
[Mon Nov 29 12:17:08 2021] vmbr1: port 18(fwpr163p0) entered forwarding state
[Mon Nov 29 12:17:08 2021] fwbr163i0: port 2(veth163i0) entered blocking state
[Mon Nov 29 12:17:08 2021] fwbr163i0: port 2(veth163i0) entered disabled state
[Mon Nov 29 12:17:08 2021] device veth163i0 entered promiscuous mode
[Mon Nov 29 12:17:09 2021] fwbr163i1: port 1(fwln163i1) entered blocking state
[Mon Nov 29 12:17:09 2021] fwbr163i1: port 1(fwln163i1) entered disabled state
[Mon Nov 29 12:17:09 2021] device fwln163i1 entered promiscuous mode
[Mon Nov 29 12:17:09 2021] fwbr163i1: port 1(fwln163i1) entered blocking state
[Mon Nov 29 12:17:09 2021] fwbr163i1: port 1(fwln163i1) entered forwarding state
[Mon Nov 29 12:17:09 2021] vmbr1: port 19(fwpr163p1) entered blocking state
[Mon Nov 29 12:17:09 2021] vmbr1: port 19(fwpr163p1) entered disabled state
[Mon Nov 29 12:17:09 2021] device fwpr163p1 entered promiscuous mode
[Mon Nov 29 12:17:09 2021] vmbr1: port 19(fwpr163p1) entered blocking state
[Mon Nov 29 12:17:09 2021] vmbr1: port 19(fwpr163p1) entered forwarding state
[Mon Nov 29 12:17:09 2021] fwbr163i1: port 2(veth163i1) entered blocking state
[Mon Nov 29 12:17:09 2021] fwbr163i1: port 2(veth163i1) entered disabled state
[Mon Nov 29 12:17:09 2021] device veth163i1 entered promiscuous mode
[Mon Nov 29 12:17:10 2021] fwbr163i2: port 1(fwln163i2) entered blocking state
[Mon Nov 29 12:17:10 2021] fwbr163i2: port 1(fwln163i2) entered disabled state
[Mon Nov 29 12:17:10 2021] device fwln163i2 entered promiscuous mode
[Mon Nov 29 12:17:10 2021] fwbr163i2: port 1(fwln163i2) entered blocking state
[Mon Nov 29 12:17:10 2021] fwbr163i2: port 1(fwln163i2) entered forwarding state
[Mon Nov 29 12:17:10 2021] vmbr1: port 20(fwpr163p2) entered blocking state
[Mon Nov 29 12:17:10 2021] vmbr1: port 20(fwpr163p2) entered disabled state
[Mon Nov 29 12:17:10 2021] device fwpr163p2 entered promiscuous mode
[Mon Nov 29 12:17:10 2021] vmbr1: port 20(fwpr163p2) entered blocking state
[Mon Nov 29 12:17:10 2021] vmbr1: port 20(fwpr163p2) entered forwarding state
[Mon Nov 29 12:17:10 2021] fwbr163i2: port 2(veth163i2) entered blocking state
[Mon Nov 29 12:17:10 2021] fwbr163i2: port 2(veth163i2) entered disabled state
[Mon Nov 29 12:17:10 2021] device veth163i2 entered promiscuous mode
[Mon Nov 29 12:17:10 2021] fwbr163i3: port 1(fwln163i3) entered blocking state
[Mon Nov 29 12:17:10 2021] fwbr163i3: port 1(fwln163i3) entered disabled state
[Mon Nov 29 12:17:10 2021] device fwln163i3 entered promiscuous mode
[Mon Nov 29 12:17:10 2021] fwbr163i3: port 1(fwln163i3) entered blocking state
[Mon Nov 29 12:17:10 2021] fwbr163i3: port 1(fwln163i3) entered forwarding state
[Mon Nov 29 12:17:10 2021] vmbr1: port 21(fwpr163p3) entered blocking state
[Mon Nov 29 12:17:10 2021] vmbr1: port 21(fwpr163p3) entered disabled state
[Mon Nov 29 12:17:10 2021] device fwpr163p3 entered promiscuous mode
[Mon Nov 29 12:17:10 2021] vmbr1: port 21(fwpr163p3) entered blocking state
[Mon Nov 29 12:17:10 2021] vmbr1: port 21(fwpr163p3) entered forwarding state
[Mon Nov 29 12:17:10 2021] fwbr163i3: port 2(veth163i3) entered blocking state
[Mon Nov 29 12:17:10 2021] fwbr163i3: port 2(veth163i3) entered disabled state
[Mon Nov 29 12:17:10 2021] device veth163i3 entered promiscuous mode
[Mon Nov 29 12:17:11 2021] fwbr163i4: port 1(fwln163i4) entered blocking state
[Mon Nov 29 12:17:11 2021] fwbr163i4: port 1(fwln163i4) entered disabled state
[Mon Nov 29 12:17:11 2021] device fwln163i4 entered promiscuous mode
[Mon Nov 29 12:17:11 2021] fwbr163i4: port 1(fwln163i4) entered blocking state
[Mon Nov 29 12:17:11 2021] fwbr163i4: port 1(fwln163i4) entered forwarding state
[Mon Nov 29 12:17:11 2021] vmbr1: port 22(fwpr163p4) entered blocking state
[Mon Nov 29 12:17:11 2021] vmbr1: port 22(fwpr163p4) entered disabled state
[Mon Nov 29 12:17:11 2021] device fwpr163p4 entered promiscuous mode
[Mon Nov 29 12:17:11 2021] vmbr1: port 22(fwpr163p4) entered blocking state
[Mon Nov 29 12:17:11 2021] vmbr1: port 22(fwpr163p4) entered forwarding state
[Mon Nov 29 12:17:11 2021] fwbr163i4: port 2(veth163i4) entered blocking state
[Mon Nov 29 12:17:11 2021] fwbr163i4: port 2(veth163i4) entered disabled state
[Mon Nov 29 12:17:11 2021] device veth163i4 entered promiscuous mode
[Mon Nov 29 12:17:11 2021] eth0: renamed from veth7Ki8JP
[Mon Nov 29 12:17:11 2021] eth1: renamed from veth3WASRU
[Mon Nov 29 12:17:11 2021] eth2: renamed from vethyCXWdt
[Mon Nov 29 12:17:11 2021] eth3: renamed from veth2itdhm
[Mon Nov 29 12:17:11 2021] net4: renamed from vethokWci7
[Mon Nov 29 12:17:11 2021] IPv6: ADDRCONF(NETDEV_CHANGE): net4: link becomes ready
[Mon Nov 29 12:17:11 2021] fwbr163i4: port 2(veth163i4) entered blocking state
[Mon Nov 29 12:17:11 2021] fwbr163i4: port 2(veth163i4) entered forwarding state
[Mon Nov 29 12:17:11 2021] IPv6: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
[Mon Nov 29 12:17:11 2021] fwbr163i3: port 2(veth163i3) entered blocking state
[Mon Nov 29 12:17:11 2021] fwbr163i3: port 2(veth163i3) entered forwarding state
[Mon Nov 29 12:17:11 2021] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[Mon Nov 29 12:17:11 2021] fwbr163i2: port 2(veth163i2) entered blocking state
[Mon Nov 29 12:17:11 2021] fwbr163i2: port 2(veth163i2) entered forwarding state
[Mon Nov 29 12:17:11 2021] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[Mon Nov 29 12:17:11 2021] fwbr163i1: port 2(veth163i1) entered blocking state
[Mon Nov 29 12:17:11 2021] fwbr163i1: port 2(veth163i1) entered forwarding state
[Mon Nov 29 12:17:11 2021] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[Mon Nov 29 12:17:11 2021] fwbr163i0: port 2(veth163i0) entered blocking state
[Mon Nov 29 12:17:11 2021] fwbr163i0: port 2(veth163i0) entered forwarding state
 

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!