From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 3FB511FF164 for ; Fri, 23 May 2025 16:45:15 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6C71F1D59C; Fri, 23 May 2025 16:45:13 +0200 (CEST) Date: Fri, 23 May 2025 16:41:25 +0200 From: Marco Gaiarin To: Proxmox VE user list Message-ID: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Organization: Casa Gaiarin User-Agent: Mutt/2.2.12 (2023-09-09) X-SPAM-LEVEL: Spam detection results: 0 AWL 0.048 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_PASS -0.1 DMARC pass policy JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] Interface not renamed... 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: , Reply-To: Proxmox VE user list Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" Mandi! Falko Trojahn In chel di` si favelave... > you surely don't have any udev rules for this interface > e.g. left over from former system? No, i've not altered in any way udev rules... Mandi! Roland In chel di` si favelave... > iirc, that can be a matter of the bios version installed. > https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf We have upgarded 8 identical servers, upgrading to identical bios version; this is the only one that have this trouble. Anyway, i've found some more info: root@svpve2:~# ip link show | egrep '[0-9]+: ' 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 2: ens1f0: mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 3: eth1: mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000 4: ens5f0np0: mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000 5: eno1: mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 6: eno2: mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000 7: ens5f1np1: mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000 8: idrac: mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000 9: bond2: mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000 10: bond0: mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000 11: vmbr0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 12: bond1: mtu 1500 qdisc noqueue master vmbr1 state UP mode DEFAULT group default qlen 1000 13: vmbr1: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 [...] interface 'ens1f1' does not desappear, simply get not 'renamed' on boot, and remain 'eth1'. I've tried a manual: ip link set eth1 master bond1 and interface start working as expected. If logs can be useful, if it is better to fire up a bug, say me. Just i'm here, i've found also: root@svpve2:~# ip addr show ens1f0 2: ens1f0: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether f4:ee:08:24:3a:ff brd ff:ff:ff:ff:ff:ff permaddr 5c:6f:69:0f:99:78 altname enp1s0f0 and 'enp1s0f0' in 'altname' was the old interface name, that was in /etc/network/interfaces; but at boot bond does not bind it, i was forced to use the 'new' name. 'altname' work only insome aspect? Or simply, does not work for bonds? Thanks. -- _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user