Differences

This shows you the differences between two versions of the page.

--- doc:appunti:linux:sa:if_rename [2023/12/15 16:26] – [With Debian 10 Buster] niccolo
+++ doc:appunti:linux:sa:if_rename [2023/12/15 16:27] – [With Debian 10 Buster] niccolo
@@ Line 15: / Line 15: @@
 **WARNING**: You cannot use this method to safely assign the default kernel names (''eth0'', ''eth1'', ...) in your preferred order; this is because if systemd tries to rename an interface using a name which is already assigned by the kernel (e.g. it tries to swap ''eth0'' and ''eth1''), it fails. So the target **Name** must not potentially conflict with the names assigned by the kernel.
-**WARNING**: This method has an additional problem if you need to create a **VLAN**. When the system creates e.g. the **lan.602**, its MAC address matches the systemd snippet, so systemd tries to assign to it the name **lan** but the name already exists, so the interface remains with a temporary name e.g. **rename5**.
+**WARNING**: This method has an additional problem if you need to create a **VLAN**. When the system creates e.g. the **lan.602**, its MAC address matches the systemd snippet, so systemd tries to assign to it the name (**lan0** in the example above) but the name already exists, so the interface remains with a temporary name e.g. **rename5**.
 A workaround can be the following: tell the kernel to use the old eth0 schema (passing the **net.ifnames=0** option), then instruct systemd to act only on **%%eth*%%** network interfaces: