Hi
I'm not a Linux expert, I spent a lot of time trying to figure out how to fix this issue.
My Proxmox server was running fine on Linux version 6.5.11-8-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40).
A few days ago, I found some updates proposed on the web interface (in the Updates folder). Among these, there were some regarding Linux - specifically, Linux version 6.5.13-1-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40). After the upgrade, Proxmox was disconnected from the network.
Looking at the dmesg logs I found that: -
on 6.5.11-8-pve the network interface name is renamed as enp1s0
Feb 22 18:49:23 pve kernel: r8169 0000:01:00.0: enabling device (0000 -> 0003)
Feb 22 18:49:23 pve kernel: r8169 0000:01:00.0 eth0: RTL8168h/8111h, XX:XX:XX:XX:XX:XX, XID 541, IRQ 125
Feb 22 18:49:23 pve kernel: r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Feb 22 18:49:23 pve kernel: r8169 0000:01:00.0 enp1s0: renamed from eth0
Feb 22 18:50:54 pve kernel: vmbr0: port 1(enp1s0) entered disabled state
Feb 22 18:50:54 pve kernel: r8169 0000:01:00.0 enp1s0: entered allmulticast mode
Feb 22 18:50:54 pve kernel: r8169 0000:01:00.0 enp1s0: entered promiscuous mode
Feb 22 18:50:54 pve kernel: Generic FE-GE Realtek PHY r8169-0-100:00: attached PHY driver (mii_bus
hy_addr=r8169-0-100:00, irq=MAC)
Feb 22 18:50:55 pve kernel: r8169 0000:01:00.0 enp1s0: No native access to PCI extended config space, falling back to CSI
Feb 22 18:50:55 pve kernel: r8169 0000:01:00.0 enp1s0: Link is Down
Feb 22 18:50:55 pve kernel: vmbr0: port 1(enp1s0) entered blocking state
Feb 22 18:50:55 pve kernel: vmbr0: port 1(enp1s0) entered forwarding state
Feb 22 18:50:58 pve kernel: r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control off
Feb 22 18:50:58 pve kernel: vmbr0: port 1(enp1s0) entered blocking state
Feb 22 18:50:58 pve kernel: vmbr0: port 1(enp1s0) entered forwarding state
on 6.5.13-1-pve the network interface name is kept as eth0
Feb 22 18:21:19 pve kernel: r8169 0000:01:00.0: enabling device (0000 -> 0003)
Feb 22 18:21:19 pve kernel: r8169 0000:01:00.0 eth0: RTL8168h/8111h, XX:XX:XX:XX:XX:XX, XID 541, IRQ 126
Feb 22 18:21:19 pve kernel: r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Feb 22 18:22:51 pve networking[714]: error: vmbr0: bridge port enp1s0 does not exist
Feb 22 18:22:51 pve /usr/sbin/ifup[714]: error: vmbr0: bridge port enp1s0 does not exist
Feb 22 18:22:51 pve networking[714]: warning: vmbr0: apply bridge ports settings: bridge configuration failed (missing ports)
Feb 22 18:22:51 pve /usr/sbin/ifup[714]: warning: vmbr0: apply bridge ports settings: bridge configuration failed (missing ports)
Feb 22 18:22:51 pve networking[714]: error: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_158_Feb-22-2024_18:22:50.740417 <<<
Feb 22 18:22:51 pve /usr/sbin/ifup[714]: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_158_Feb-22-2024_18:22:50.740417 <<<
Feb 22 18:22:51 pve systemd[1]: Finished networking.service - Network initialization.
To fix the issue on 6.5.13-1-pve I had to change the file /etc/systemd/network/10-enp1s0.link as:
[Match]
MACAddress=XX:XX:XX:XX:XX:XX
[Link]
WakeOnLan=magic
Name=enp1s0
I'm not sure if this is the correct way to fix the issue, or if it will continue to work in future Linux updates
Thanks
Alex
I'm not a Linux expert, I spent a lot of time trying to figure out how to fix this issue.
My Proxmox server was running fine on Linux version 6.5.11-8-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40).
A few days ago, I found some updates proposed on the web interface (in the Updates folder). Among these, there were some regarding Linux - specifically, Linux version 6.5.13-1-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40). After the upgrade, Proxmox was disconnected from the network.
Looking at the dmesg logs I found that: -
on 6.5.11-8-pve the network interface name is renamed as enp1s0
Feb 22 18:49:23 pve kernel: r8169 0000:01:00.0: enabling device (0000 -> 0003)
Feb 22 18:49:23 pve kernel: r8169 0000:01:00.0 eth0: RTL8168h/8111h, XX:XX:XX:XX:XX:XX, XID 541, IRQ 125
Feb 22 18:49:23 pve kernel: r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Feb 22 18:49:23 pve kernel: r8169 0000:01:00.0 enp1s0: renamed from eth0
Feb 22 18:50:54 pve kernel: vmbr0: port 1(enp1s0) entered disabled state
Feb 22 18:50:54 pve kernel: r8169 0000:01:00.0 enp1s0: entered allmulticast mode
Feb 22 18:50:54 pve kernel: r8169 0000:01:00.0 enp1s0: entered promiscuous mode
Feb 22 18:50:54 pve kernel: Generic FE-GE Realtek PHY r8169-0-100:00: attached PHY driver (mii_bus
hy_addr=r8169-0-100:00, irq=MAC)Feb 22 18:50:55 pve kernel: r8169 0000:01:00.0 enp1s0: No native access to PCI extended config space, falling back to CSI
Feb 22 18:50:55 pve kernel: r8169 0000:01:00.0 enp1s0: Link is Down
Feb 22 18:50:55 pve kernel: vmbr0: port 1(enp1s0) entered blocking state
Feb 22 18:50:55 pve kernel: vmbr0: port 1(enp1s0) entered forwarding state
Feb 22 18:50:58 pve kernel: r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control off
Feb 22 18:50:58 pve kernel: vmbr0: port 1(enp1s0) entered blocking state
Feb 22 18:50:58 pve kernel: vmbr0: port 1(enp1s0) entered forwarding state
on 6.5.13-1-pve the network interface name is kept as eth0
Feb 22 18:21:19 pve kernel: r8169 0000:01:00.0: enabling device (0000 -> 0003)
Feb 22 18:21:19 pve kernel: r8169 0000:01:00.0 eth0: RTL8168h/8111h, XX:XX:XX:XX:XX:XX, XID 541, IRQ 126
Feb 22 18:21:19 pve kernel: r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Feb 22 18:22:51 pve networking[714]: error: vmbr0: bridge port enp1s0 does not exist
Feb 22 18:22:51 pve /usr/sbin/ifup[714]: error: vmbr0: bridge port enp1s0 does not exist
Feb 22 18:22:51 pve networking[714]: warning: vmbr0: apply bridge ports settings: bridge configuration failed (missing ports)
Feb 22 18:22:51 pve /usr/sbin/ifup[714]: warning: vmbr0: apply bridge ports settings: bridge configuration failed (missing ports)
Feb 22 18:22:51 pve networking[714]: error: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_158_Feb-22-2024_18:22:50.740417 <<<
Feb 22 18:22:51 pve /usr/sbin/ifup[714]: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_158_Feb-22-2024_18:22:50.740417 <<<
Feb 22 18:22:51 pve systemd[1]: Finished networking.service - Network initialization.
To fix the issue on 6.5.13-1-pve I had to change the file /etc/systemd/network/10-enp1s0.link as:
[Match]
MACAddress=XX:XX:XX:XX:XX:XX
[Link]
WakeOnLan=magic
Name=enp1s0
I'm not sure if this is the correct way to fix the issue, or if it will continue to work in future Linux updates
Thanks
Alex
Last edited: