From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DDDA4C4332F for ; Thu, 14 Dec 2023 14:50:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1573548AbjLNOut (ORCPT ); Thu, 14 Dec 2023 09:50:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50538 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1573561AbjLNOui (ORCPT ); Thu, 14 Dec 2023 09:50:38 -0500 Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8E55B126 for ; Thu, 14 Dec 2023 06:50:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=kRql+GwSPznHnnIwuDv3FvENld3LuUCkNpS6nae+YqY=; b=ATq1vHA0MEpgy24y9rXI/050ovv08oShUpGXhCAnr4ddbqGqbYYTEiuy xR8JPnLrwbfOaSrrWOazlah1TaZyCMtDqY66V0HGhm7gnru+qqJiSQ6yE T/Dxk+rp+KxnzluPnASH5ClzjwKakKs+GnoIE6WlzwXDFJ+GSW3GG7bnx Y=; Authentication-Results: mail2-relais-roc.national.inria.fr; dkim=none (message not signed) header.i=none; spf=SoftFail smtp.mailfrom=julia.lawall@inria.fr; dmarc=fail (p=none dis=none) d=inria.fr X-IronPort-AV: E=Sophos;i="6.04,275,1695679200"; d="scan'208";a="142332816" Received: from 231.85.89.92.rev.sfr.net (HELO hadrien) ([92.89.85.231]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Dec 2023 15:50:41 +0100 Date: Thu, 14 Dec 2023 15:50:41 +0100 (CET) From: Julia Lawall X-X-Sender: jll@hadrien To: Ivan Vecera cc: "David S. Miller" , linux-kernel@vger.kernel.org Subject: Re: Failed to start Raise network interfaces error In-Reply-To: <4a053d6a-92c6-4d01-bfe5-2349d64cc429@redhat.com> Message-ID: References: <21977757-3a63-4586-ae03-e6630c1f009d@redhat.com> <4c707e3e-a324-a5e6-dc21-833b6d40324d@inria.fr> <88a7a623-ad80-406c-a63b-3136df963888@redhat.com> <4a053d6a-92c6-4d01-bfe5-2349d64cc429@redhat.com> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 14 Dec 2023, Ivan Vecera wrote: > On 14. 12. 23 15:33, Julia Lawall wrote: > > > > > > 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. > > In this case, you can configure custom udev rule that will fix the name of the > interface... Like: > > host ~ # cat /etc/udev/rules.d/70-network.rules > ACTION=="add", SUBSYSTEM=="net", DRIVERS=="i40e",\ > ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="enp24s0f0" > ACTION=="add", SUBSYSTEM=="net", DRIVERS=="i40e",\ > ATTR{address}=="yy:yy:yy:yy:yy:yy", NAME="enp24s0f1" Thanks! julia