Strange Small issue need help with.

Calum.mck

New Member
Mar 2, 2025
1
0
1
Today I was having some issue with getting pveam update to work. I was getting errors:
download failed: 500 Can't connect to download.proxmox.com:80 (Temporary failure in name resolution)
2025-03-01 05:48:03 update failed - no signature file '/var/lib/pve-manager/apl-info/pveam-download.proxmox.com.tmp.107664.asc'

It was pretty clear the issue was some sort of connectivity issue.

Luckily, after messing around with some pings and such in the proxmox shell and an internal VM's shell. I was able to see that Proxmox was using an interface called "vmbr2." This was not the interface I had intended to use, "vmbr0". By changing some network configs and moving a couple wires around, I was able to update and move forward, technically.

However, the interface vmbr2 is currently stuck as the '"PROXMOX UPDATE'S INTERFACE'" for lack of better words. It is intended to be a separate bridge for my CISCO lab VMs. I have another "vmbr1" on the same card dedicated to a Truenas VM it's solid. I can in the short term, live with remembering to move things around and re-configure when I need to update proxmox, download container lists, or generally access the internet via proxmox's shell but that is a pain.

I have 3 interfaces configured on this rig, vmbr0, vmbr1, and vmbr2. Vmbr2 seems to be the one proxmox has chosen for it's self. Is there some way to select a different interface to do this over?
 
May be it is a gateway issue? The system will use the interface with default route on it configured. I assume, vmbr2 has a gateway configured. What about the other two vmbr*?
Would you like to post the content of /etc/network/interfaces file of the proxmox node?