Thank you for this suggestion. I don't think it's that easy, though. Especially when netplan is run as a systemd-generator during early boot (i.e. the default use case).
The generator is not using "ip link set ..." to change the name, but rather defines udev rules to make the rename happen. We'd need to have some multi-staged udev rules like this:
If interface is supposed to be renamend:
1) re-name to something temporary "netplan-RANDOM_STRING" and remember the association with the netplan ID, this is to avoid conflicts if the new name would already exist.
2) re-name again (after all re-names moved to a temporary name), to the actual "set-name" value.
Thank you for this suggestion. I don't think it's that easy, though. Especially when netplan is run as a systemd-generator during early boot (i.e. the default use case).
The generator is not using "ip link set ..." to change the name, but rather defines udev rules to make the rename happen. We'd need to have some multi-staged udev rules like this:
If interface is supposed to be renamend: RANDOM_ STRING" and remember the association with the netplan ID, this is to avoid conflicts if the new name would already exist.
1) re-name to something temporary "netplan-
2) re-name again (after all re-names moved to a temporary name), to the actual "set-name" value.
I'm marking this as a whishlist item.