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 3D8EB1FF16F for ; Tue, 27 May 2025 22:50:37 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4EEF01E52E; Tue, 27 May 2025 22:50:45 +0200 (CEST) Date: Tue, 27 May 2025 22:46:20 +0200 From: Marco Gaiarin To: pve-user@lists.proxmox.com Message-ID: References: <9af42a93-1eaa-4b19-b3de-db371fba6e50@proxmox.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <9af42a93-1eaa-4b19-b3de-db371fba6e50@proxmox.com> Organization: Casa Gaiarin User-Agent: Mutt/2.2.12 (2023-09-09) X-SPAM-LEVEL: Spam detection results: 0 AWL 0.307 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 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] 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! Fiona Ebner In chel di` si favelave... > see also: > https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_naming_conventions > > The recommended way to avoid such renaming issues is to pin the name > based on MAC address: > https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#network_override_device_names Thanks, Fiona; but it is not the renaming 'per se' that scare me, was written in the documentation, i was prepared of. But probably i've found the culprit. Systems get installed in some PVE 6.X version, and have a direct bond between two nodes to manage replication and migration; in PVE6 we had some trouble to setup jumbo frames for the bond, because some times the server boot with MTU=9000 on the bond but not on the member link. We solved it adding 'allow-bond2' to the member stanzas on /etc/network/interfaces. Seems to me that: 1) PVE 7 effectively rename interfaces; as just stated, this is expected, no trouble. 2) PVE 8 add 'ifupdown2', that is incompatible with 'allow-bond2' option AND in some way ''mangle' all the ifupdown -> ifupdown2 migration: server boot with NO interface up, but also some other things seems does not work very well. Because i've still some server to migrate, i've removed 'allow-bond2' options BEFORE initiate the upgrade PVE7 -> 8, and migration went smoothly, precisely: - interface start at next boot - all interfece went up, even get renamed, because 'altname' get correctly used. I hope i was clear. And useful. ;-) -- _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user