On Sb, 06 apr 19, 10:28:15, Karl O. Pinc wrote: > C) Actual upgrade instructions. This is in-progress. > > There are really 2 paths for manual migration of > interface names: one for when you have console/physical > access and another when you don't. In the first case, > you can try the new names, see what name you get, and > migrate /etc/. Without console access you need to > calculate the new interface name, migrate, and hope > you got the right name after reboot. To calculate > the right interface name you need additional background > information. I've whacked up a teeny script, with > no dependencies, to compute the common case. But it > does require the pciid as input, and I suggest installing > pciutils to get lspci to find pciids. According to [1] here are two other options: 3. assign own names (e.g. internet0, dmz0, lan0, etc.) by creating a .link file in /etc/systemd/network/ and migrate your configuration accordingly. 4. disable the naming policy (via kernel parameter or udev) and optionally migrate later (e.g. when one has console access to the system). It should be possible to use the kernel parameter in combination with a "boot once" grub entry to both get the new name and test the new configuration for remote systems. Wouldn't it make sense to ask also the udev/systemd maintainers for input? [1] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
Attachment:
signature.asc
Description: PGP signature