From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 4CD358A43A for ; Tue, 2 Aug 2022 12:29:18 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 43E5537597 for ; Tue, 2 Aug 2022 12:29:18 +0200 (CEST) Received: from mail-yw1-x1133.google.com (mail-yw1-x1133.google.com [IPv6:2607:f8b0:4864:20::1133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 2 Aug 2022 12:29:16 +0200 (CEST) Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-324293f1414so101147447b3.0 for ; Tue, 02 Aug 2022 03:29:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=CIKuE89cYfSdBY4IGVeHnx9XiAImezWBOGin8pnZFhc=; b=DB4H98Qo1FSxKhYRLbASGDUZO0B/acz+fJijKG1wPwcvH/+ehTtDO7PtqMzogYkcgW fOcN5hzJMmj6LhlARb2x1lWXjj6/hDtONJgvilniThvgAsxOeSHNv2Df3Qmn+lFUxyWF I+VmGrWJS0VZYt+rS1u8aQy0NbkNTVdPw4KRG3Z4w235MXJgfqPE1Oe1a9qWPuKm9LxV SFUuL0rFNd/XUaq3zDyh6GUV6T/WdbAWKMyL10X6/okHNn1qZIDE4gV8KQmdoByyD6gb XunqG/foDUrPH1a55P0CzlfY44uzk8nvPAS+rNGjyCb9pnY7YfB7UlJl40TZ2hNv6PWD wkxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=CIKuE89cYfSdBY4IGVeHnx9XiAImezWBOGin8pnZFhc=; b=i+NvsItqlpJa/OKZSIZunO+dbLtCaPVHjkWCm4NtaTvdjroxZX8tp+VPTlbz0Zwygq wPb5HuJ0rQ5EEMHKDc8DrXfTcrIzjD4+bj1pWJ4mRUvbj7gd5MY63k21Xq47hpCQ+Wxd q7D/+UuV6o5riDlUXQKvlvaxRWXckhaUfIVCyaqorJcRffWi0xN2GGKhA/qz16eK05kF C+0OVToJzd2xYsGA3V7gKDXqTV7oaVPMY4ogWMlsgQdst/wODIt+eDrERCiPRDvw/Zsn rxQeQlQbGNZlcPPU4w7zAw8L9HCV/brOUn//78CI6R1JEIWAqeNWQPqU29e8G+yeugqW Qbeg== X-Gm-Message-State: ACgBeo0taJAs1RSVd31iRDPj0EqHzG6hMaqjKm/RqbvVmCAEoHIMguSr tnzpXPGvHA3rbiLjTA3wm0GDyc4PSgGUZKHt0mTD8+siaP/8Rs5U X-Google-Smtp-Source: AA6agR7urX1/lV/cr4rqcWghz0ZbL9b0nYW4zYl5wypgKAO1X/PA1Jr0xexrFyX/Hc5z7ldbga+rl+7UJuwTU0dFiJ8= X-Received: by 2002:a81:5c05:0:b0:31f:61e4:8ea1 with SMTP id q5-20020a815c05000000b0031f61e48ea1mr17929183ywb.377.1659436148558; Tue, 02 Aug 2022 03:29:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kalpesh Sejpal Date: Tue, 2 Aug 2022 15:58:57 +0530 Message-ID: To: pve-user@lists.proxmox.com X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years POISEN_SPAM_PILL_4 0.1 random spam to be learned in bayes RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_MIME_MALF 0.01 Malformed MIME: headers in body URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com, pm.me, binovo.es, 10-management.link, linet-services.de] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-Mailman-Approved-At: Wed, 03 Aug 2022 09:42:31 +0200 Subject: Re: [PVE-User] pve-user Digest, Vol 173, Issue 1 X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Aug 2022 10:29:18 -0000 it should be possible to prevent a change of the interface names with, for example, a custom .link file, see here: https://wiki.debian.org/NetworkInterfaceNames#custom Regards, kalpesh sejpal On Tue, 2 Aug, 2022, 3:30 pm , wrote: > Send pve-user mailing list submissions to > pve-user@lists.proxmox.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > or, via email, send a message with subject or body 'help' to > pve-user-request@lists.proxmox.com > > You can reach the person managing the list at > pve-user-owner@lists.proxmox.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of pve-user digest..." > > > Today's Topics: > > 1. PVE 6 to 7 BCM57412 devices name change (Eneko Lacunza) > 2. Re: PVE 6 to 7 BCM57412 devices name change (Stephan Leemburg) > 3. Re: PVE 6 to 7 BCM57412 devices name change (Arjen) > 4. Re: PVE 6 to 7 BCM57412 devices name change (Bastian Sebode) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 1 Aug 2022 14:27:04 +0200 > From: Eneko Lacunza > To: Proxmox VE user list > Subject: PVE 6 to 7 BCM57412 devices name change > Message-ID: <35969752-f65f-4000-4890-503e5c61a809@binovo.es> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi all, > > I have noticed that when upgrading from PVE 6.4 to 7.2, BCM57412 network > devices change name, i.e.: > > ens2f0np0 -> enp101s0f0np0 > > Devices are seen like: > 65:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 > NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01) > 65:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 > NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01) > > I have seen this in 3 different servers until now (all Dell PowerEdge). > > This can be an issue if upgrading remotely (I was today, had to resort > to? iDRAC virtual console). > > Has anyone seen this? Is there a way to know what the new name will be, > so that /etc/network/interfaces can be changed accordingly? > > Shall I suggest a change in 6to7 wiki? > > Thanks! > > Eneko Lacunza > Zuzendari teknikoa | Director t?cnico > Binovo IT Human Project > > Tel. +34 943 569 206 |https://www.binovo.es > Astigarragako Bidea, 2 - 2? izda. Oficina 10-11, 20180 Oiartzun > > https://www.youtube.com/user/CANALBINOVO > https://www.linkedin.com/company/37269706/ > > > ------------------------------ > > Message: 2 > Date: Mon, 1 Aug 2022 19:45:19 +0200 > From: Stephan Leemburg > To: pve-user@lists.proxmox.com > Subject: Re: [PVE-User] PVE 6 to 7 BCM57412 devices name change > Message-ID: <9d90626b-7fcf-66fa-fe28-9691a665c37a@it-functions.nl> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi Eneko, > > We used to use net.ifnames=0 but where getting very unpredictable results. > > So we switched to using /etc/systemd/network/*.link files with logical > naming. > > You can use > > ?udevadm test-builtin net_id /sys/class/net/$INTERFACENAME > > where INTERFACENAME is the interface you want to have the attributes of. > > Then you can - for example - use: > > ?cat /etc/systemd/network/10-management.link > > ?[Match] > ?Property=ID_NET_NAME_PATH=enp130s0f3 > > ?[Link] > ?AlternativeNamesPolicy=onboard path > ?Name=management > > For logically naming the devices. Do remember to run > > ?update-initramfs -u -k $(uname -r) > > or > > ?update-initramfs -u -k all > > Hope that helps. > > Best regards, > > Stephan > > On 01-08-2022 14:27, Eneko Lacunza via pve-user wrote: > > _______________________________________________ > > pve-user mailing list > > pve-user@lists.proxmox.com > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > > ------------------------------ > > Message: 3 > Date: Mon, 01 Aug 2022 18:16:40 +0000 > From: Arjen > To: Proxmox VE user list > Subject: Re: [PVE-User] PVE 6 to 7 BCM57412 devices name change > Message-ID: > > pm.me> > > Content-Type: text/plain; charset=utf-8 > > On Monday, August 1st, 2022 at 14:27, Eneko Lacunza via pve-user < > pve-user@lists.proxmox.com> wrote: > > > Hi all, > > > > I have noticed that when upgrading from PVE 6.4 to 7.2, BCM57412 network > > devices change name, i.e.: > > > > ens2f0np0 -> enp101s0f0np0 > > > > Devices are seen like: > > 65:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 > > NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01) > > 65:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 > > NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01) > > > > I have seen this in 3 different servers until now (all Dell PowerEdge). > > > > This can be an issue if upgrading remotely (I was today, had to resort > > to? iDRAC virtual console). > > > > Has anyone seen this? Is there a way to know what the new name will be, > > so that /etc/network/interfaces can be changed accordingly? > > Something like this is mentioned in the Changelog Overview of PVE 7.0: > https://pve.proxmox.com/wiki/Roadmap#7.0-known-issues > > > Shall I suggest a change in 6to7 wiki? > > It does not appear to be mentioned here: > https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Network > Which is unexpected, so yes please. > > > Thanks! > > > > Eneko Lacunza > > Zuzendari teknikoa | Director t?cnico > > Binovo IT Human Project > > > > Tel. +34 943 569 206 |https://www.binovo.es > > Astigarragako Bidea, 2 - 2? izda. Oficina 10-11, 20180 Oiartzun > > > > https://www.youtube.com/user/CANALBINOVO > > https://www.linkedin.com/company/37269706/ > > > > ------------------------------ > > Message: 4 > Date: Tue, 2 Aug 2022 00:42:45 +0200 > From: Bastian Sebode > To: Eneko Lacunza , Proxmox VE user list > > Subject: Re: PVE 6 to 7 BCM57412 devices name change > Message-ID: > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi Eneko, > > I had the same issue when doing that upgrade on a cluster. On the first > node I noticed the problem and fixed it over the virtual console. After > that I noted the changes and right before the reboot of the following > nodes I replaced the occurrences in /etc/network/interfaces accordingly > to have a functional system after the reboot. > > Unfortunately I'm not aware of how you could know these changes prior > updating/rebooting the first node or single server. > > Peace > Bastian > > Am 01.08.2022 um 14:27 schrieb Eneko Lacunza: > > Hi all, > > > > I have noticed that when upgrading from PVE 6.4 to 7.2, BCM57412 > > network devices change name, i.e.: > > > > ens2f0np0 -> enp101s0f0np0 > > > > Devices are seen like: > > 65:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 > > NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01) > > 65:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57412 > > NetXtreme-E 10Gb RDMA Ethernet Controller (rev 01) > > > > I have seen this in 3 different servers until now (all Dell PowerEdge). > > > > This can be an issue if upgrading remotely (I was today, had to resort > > to? iDRAC virtual console). > > > > Has anyone seen this? Is there a way to know what the new name will > > be, so that /etc/network/interfaces can be changed accordingly? > > > > Shall I suggest a change in 6to7 wiki? > > > > Thanks! > > > > Eneko Lacunza > > Zuzendari teknikoa | Director t?cnico > > Binovo IT Human Project > > > > Tel. +34 943 569 206 |https://www.binovo.es > > Astigarragako Bidea, 2 - 2? izda. Oficina 10-11, 20180 Oiartzun > > > > https://www.youtube.com/user/CANALBINOVO > > https://www.linkedin.com/company/37269706/ > > -- > Bastian Sebode > Fachinformatiker Systemintegration > > LINET Services GmbH | Cyriaksring 10a | 38118 Braunschweig > Tel. 0531-180508-0 | Fax 0531-180508-29 | http://www.linet-services.de > > LINET in den sozialen Netzwerken: > www.twitter.com/linetservices | www.facebook.com/linetservices > Wissenswertes aus der IT-Welt: www.linet-services.de/blog/ > > Gesch?ftsf?hrung: Timo Springmann, Mirko Savic und Moritz Bunkus > HR B 9170 Amtsgericht Braunschweig > > USt-IdNr. DE 259 526 516 > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > ------------------------------ > > End of pve-user Digest, Vol 173, Issue 1 > **************************************** > >