linux-kernel - Re: Failed to start Raise network interfaces error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 14 Dec 2023 15:33:28 +0100 (CET)
From:   Julia Lawall <julia.lawall@...ia.fr>
To:     Ivan Vecera <ivecera@...hat.com>
cc:     "David S. Miller" <davem@...emloft.net>,
        linux-kernel@...r.kernel.org
Subject: Re: Failed to start Raise network interfaces error



On Tue, 12 Dec 2023, Ivan Vecera wrote:

>
>
> On 12. 12. 23 17:33, Julia Lawall wrote:
> > > Look at 'systemd.net-naming-scheme' man page for details how the interface
> > > names are composed.
> > After booting into 6.7.0-rc4, I have the following in
> > /etc/network/interfaces:
> >
> > # This file describes the network interfaces available on your system
> > # and how to activate them. For more information, see interfaces(5).
> >
> > source/etc/network/interfaces.d/*
> >
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> >
> > auto enp24s0f0
> > iface enp24s0f0 inet dhcp
>
> Just change 'enp24s0f0' in /etc/network/interfaces to 'enp24s0f0np0'

Hello,

I don't know if anything can be done about it, but this change introduces
complexities.  The people who manage the cluster that I use say that the
name of the network interface should be predictable, which is no longer
the case because it now depends on the kernel version.

thanks,
julia