On Tue, Dec 27, 2016 at 1:53 PM, lee <l...@yagibdah.de> wrote: > Neil Bothwick <n...@digimed.co.uk> writes: >> >> There is nothing wrong with wanting things to work as you do, but it >> requires input to do so. It you have to start editing files to make >> it work properly, there is little point in making it the default. > > Right, and it could work without editing files manually. A > configuration file assigning editable names to the annoying names > could be created automatically and filled by assigning the name an > interface already has to it (because when it has a name, the name is > known, which is easier than trying to make up all possible names in > advance). Then only if you wanted you would edit the configuration > file to assign the name(s) of your choosing, and if you don't want to > do that, you simply get the names you get now. There would be no > change to how the names are now, only an additional option. > > That would also have the advantage that when the annoying name of an > interface changes, you can choose to either adjust all configuration > files in which you have specified a particular interface or simply > adjust the one configuration file that assigns the names.
There are two ways to ensure that you always have the kernel's names: 1) Add "net.ifnames=0" to the kernel cmdline 2) Override "NamePolicy=..." in "/lib/systemd/network/99-default.link" with "NamePolicy=kernel" in "/etc/systemd/network/99-default.link".