Not-so-predictable network names

[Alexander Thomas]

I have another workaround that allows to use the new network names,
even when doing a pure USB/DVD install with no working network
connection:

In the jessie NFSroot etc/grub.cfg, add “net.ifnames=1 biosdevname=1”
to the kernel command line, to mimic the defaults from Ubuntu.
In scripts/DEBIAN/30-interface, override NIC1 as follows:
NIC1=$(lshw -C network | grep 'logical name: ' | head -n 1 | awk '{print $3}')

This assumes the first interface shown by lshw is the one you want,
which was the case on the few systems I tried this on. Your mileage
may vary :)

On Fri, Aug 5, 2016 at 1:07 AM, andrew bezella <abezella at archive.org> wrote:
> On Thu, 2016-08-04 at 22:20 +0200, Thomas Lange wrote:
> [...]
>> I'm not sure if the kernel version or systemd or both are responsible
>> for this. You may want to try a 4.x kernel from backports inside the
>> nfsroot. Here's how to install the 4.x kernel inside the nfsroot:
>> http://wiki.fai-project.org/wiki/Grml_Kernel
>
> fwiw i'm running the linux-image-4.4.6-fai-amd64 kernel and systemd
> 228-6 (needed an update for disk/by-path support) in my jessie nfsroot.
> nfsbooted, the network cards show up as eth0 & eth1.  once the install
> is complete and the node is up as xenial they appear as enp3s0 & enp3s1
> (or enp7s0f0 on different hw).
>
> --
> andrew bezella <abezella at archive.org>
> Internet Archive



-- 
Alexander Thomas

Senior Developer


eSATURNUS

T. +32 16 40 12 82

www.esaturnus.com