Thanks for your feedback, and yeah changes in kernel release, systemd version and moving around HW can unfortunately result in such name changes. IME the ones from kernel updates stabilize once all features of a HW are supported correctly and no new issues come up.
One thing to avoid such changes is to pin the name of the interfaces manually. E.g., one could name a network interfacenet0
through matching their MAC address in a/etc/systemd/network/00-net0.link
configuration like:
Code:[Match] MACAddress=aa:bb:cc:12:34:56 [Link] Name=net0
This is something that might be worth to expose as option in our installer.
Edit: change frometh0
tonet0
for the example to avoid potential race between kernel and udev.
Hi, so in preparation for version 8.2 I tried to implement this in 8.1 now - it does seem to have worked at least partially (ip a shows updated physical interface name, web portal shows old name still), but there seem to be some issues with this due to the MAC being the same for the physical port (enp1s0; that should actually be renamed) as well as the bridge/VLAN devices (vmbr0, vmbr0.10) that it's part of?
Code:
Apr 22 15:56:03 pve (udev-worker)[1427]: lan0: Failed to rename network interface 5 from 'vmbr0.10' to 'lan0': File exists
Apr 22 15:56:03 pve (udev-worker)[1427]: lan0: Failed to process device, ignoring: File exists
Apr 22 15:56:04 pve networking[1413]: error: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_191_Apr-22-2024_15:56:02.352760 <<<
Apr 22 15:56:04 pve /usr/sbin/ifup[1413]: >>> Full logs available in: /var/log/ifupdown2/network_config_ifupdown2_191_Apr-22-2024_15:56:02.352760 <<<
Update:
as per https://utcc.utoronto.ca/~cks/space/blog/linux/NetworkdMACMatchesWidely , the link file should thus probably also include a "Type" match, such that
Code:
[Match]
MACAddress=xxxx
Type=<one of: ether, wlan, wwan>
[Link]
Name=<your preferred name>
Last edited: