tsimblist

I agree about simplifying my network setup. Proxmox has leveraged the /etc/network/interfaces file for some serious networking functionality. It defaults to a simple network with a Linux bridge for virtual nics. As my homelab grew, I moved to Open vSwitch which uses the same Web GUI page and interfaces file underneath. Now Proxmox has Software-Defined Network which I should probably migrate to given I currently have eight servers in a cluster with the RPi5 tentatively making number nine. It appears they are still using /etc/network/interfaces with SDN. All of my AMD64 homelab servers were loaded with Proxmox VE installer ISOs. Proxmox uses Ubuntu Linux kernels for the ZFS support, Debian user space and the Proxmox VE hypervisor for KVM/QEMU, LXC and the Web GUI.. I had intended to do the same thing for my RPi5 using this guide: Install Proxmox ARM64 on a Raspberry Pi 5 This Weekend That's why I bought the RPi5 in the first place. But it did not work for me as advertised, so I found Armbian which got me so much farther down the road along with better functionality. However I do have to troubleshoot things like networking config conflicts and ZFS not working. I also use serial consoles for most of my servers for the same reason, a way to fix network problems when the Web GUI is down.

Thank you for the heads up. I had to shutdown netplan so that Proxmox could use /etc/network/interfaces for the network configuration.

Thank you for your reply. It helped me review my assumptions. Like I assumed that this was an Armbian issue because it didn't properly install/upgrade the ifupdown2 package from the Proxmox repo. But I was unable to list that package from that repo. It only appeared in the Debian repo. So I loaded the Proxmox VE ARM installer ISO into an Ubuntu VM that I had in my homelab and found the missing package and copied it to the RPI5B and installed it. Problem solved. Thank you for your support.

Installed minimal debian image on my rPI5B. Then used "armbian-config --cmd PVE001" to install Proxmox. That went well with no reported errors. Navigated to the Proxmox web GUI and it looked and acted as expected. I currently have an AMD64 Proxmox cluster operating on my homelab so I am familiar with Proxmox. I wanted to make some changes to my network configuration using the Proxmox GUI. When I clicked the "Apply Configuration" button, it threw an "incompatible ifupdown2 package version" instead of applying the configuration.