doc:appunti:linux:sa:if_rename
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
doc:appunti:linux:sa:if_rename [2021/12/13 09:38] – [With Debian 10 Buster] niccolo | doc:appunti:linux:sa:if_rename [2024/04/12 18:01] (current) – [Debian 9 predictable network interface names] niccolo | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== With Debian 10 Buster ===== | ===== With Debian 10 Buster ===== | ||
- | According some sources, there is at least two methods | + | How to rename a network interface |
- | + | ||
- | The simplest | + | |
- | + | ||
- | < | + | |
- | rename enx00e04c885302=lan0 | + | |
- | </ | + | |
- | + | ||
- | Another methos should be to create a file **/ | + | |
< | < | ||
Line 21: | Line 13: | ||
</ | </ | ||
- | The systemd method has a problem if you need to create a **VLAN**. When the system creates e.g. the **lan.602**, | + | **WARNING**: |
+ | |||
+ | **WARNING**: | ||
- | 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: | + | A workaround can be the following: tell the kernel to use the old '' |
< | < | ||
Line 125: | Line 119: | ||
SUBSYSTEM==" | SUBSYSTEM==" | ||
</ | </ | ||
+ | |||
+ | :!: **ATTENZIONE**: | ||
+ | |||
+ | :!: **ATTENZIONE**: | ||
+ | |||
===== Debian 9 Network Interface Naming ===== | ===== Debian 9 Network Interface Naming ===== | ||
doc/appunti/linux/sa/if_rename.txt · Last modified: 2024/04/12 18:01 by niccolo