gpg: Signature made Sun Apr 3 17:55:09 2022 UTC
gpg: using DSA key 0E4236CB52951E14536066222099B64CBF15490B
gpg: Good signature from "Andy Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andrew James Smith <andy@strugglers.net>" [unknown]
gpg: aka "Andy Smith (UKUUG) <andy.smith@ukuug.org>" [unknown]
gpg: aka "Andy Smith (BitFolk Ltd.) <andy@bitfolk.com>" [unknown]
gpg: aka "Andy Smith (Linux User Groups UK) <andy@lug.org.uk>" [unknown]
gpg: aka "Andy Smith (Cernio Technology Cooperative) <andy.smith@cernio.com>" [unknown]
Hello,
The version of udev that will come with the next Debian stable and
Ubuntu LTS releases has learned about Xen network interfaces and as
a result they will be subjected to "predictable network interface
naming":
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
That is, you won't have an eth0 any more, it will be en123abc or
whatever, based on MAC address.
For new installs, either when ordered or when the customer does an
install via Xen Shell, we could force this to not happen by using
net.ifnames=0 on the kernel command line. The single network
interface will then always be eth0.
Arguments in favour of doing this:
- It makes life simpler for BitFolk's post-installation scripts
because they won't have to work out what the network interface
will be called.
- "predictable network interface names" are arguably pointless in
the scenario of a BitFolk VM because the only way to get extra
network interfaces is by explicit configuration either within the
VM by its admin or outside the VM by BitFolk, which would include
what its name is.
Arguments against:
- It's not the default behaviour of the Linux distribution any more.
- If you upgraded a previous release with dist-upgrade /
do-release-upgrade it would get these "predictable names", which
is maybe just an extension of the above point.
Would you have any concerns if you made a new order or did a new
install and it came with net.ifnames=0?
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
