Renaming Network Interfaces with Systemd in Proxmox 8.2.2

[RadoslavVassilev]

Hi Guys,

We have recently deployed a Proxmox 8.2.2 in a clustered setup currently consisting of two nodes. We are aiming to standardize Network Interfaces, bonds and bridge configurations. Currently we've created link files in /etc/systemd/network/ for each physical network interface. These files match the network interface based on specific attributes (like MAC address) and assign a custom name to each interface.

For instance, renaming enp2s0f1 to mgmt1 by creating a file 30-mgmt1.link. The file includes [Match] and [Link] sections to match the MAC address and specify the new name.

Example:​

​

[Match]​

MACAddress=c4:34:6b:b7:73:49​

Type=ether​

​

[Link]​

Name=mgmt1​

We can successfully build bonds and bridges on top of this configuration following the standard guideline for /etc/network/interfaces and that works just fine.

The issue we are facing is that the GUI does not recognize the network type and displays "Unknown" as you can see below:



Is there a separate identification/validation mechanism for the GUI that we are not following?

Thanks in advance for your support!

 

[mariol]

Only a certain schema is read by GUI [1]. As you have already correctly recognized, the correct function is not affected by this.

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#systemd_network_interface_names

 

[Maximiliano]

Hello,

At the moment Proxmox VE assumes that ifupdown is used to manage the network config of the host. Others as systemd-networkd are not supported as of now.

You can probably use most of Proxmox VE using system-networkd instead of ifupdown as it is just a mean for configuring the network, however this is not supported by us and many of the features of the web UI won't work as expected.

 

[vlan2540]

I was struggling with that too, but I managed to get it working. To be recognized as an interface, it must either be named eth[n] or start with "en"
So enmgmt1, enmgmt2, ... would solve the problem.

Here is the documentation where i found the solution.
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_naming_conventions

I hope this helps!