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 C0205839B for ; Thu, 27 Jul 2023 08:21:08 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 943696F44 for ; Thu, 27 Jul 2023 08:21:08 +0200 (CEST) Received: from ip1-isp1-algemesi.verdnatura.es (ip1-isp1-algemesi.verdnatura.es [195.77.191.178]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 ; Thu, 27 Jul 2023 08:21:06 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ip1-isp1-algemesi.verdnatura.es (Postfix) with ESMTP id 14276A00A0 for ; Thu, 27 Jul 2023 08:21:00 +0200 (CEST) Authentication-Results: ip1-isp1-algemesi.verdnatura.es (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=verdnatura.es DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verdnatura.es; h= content-transfer-encoding:content-type:content-type:message-id :references:in-reply-to:subject:subject:from:from:date:date :mime-version:received:received; s=mail; t=1690438859; bh=JLd12i DqT88dpCFiNRZzeYUJpXL2s6uMi0bf0tq4+tM=; b=KieK1JNTPKhf8NhY6CjDXy GubGLtfH3NgH2l+Qlp8mvX1f32BaxbLN9RkCNOkOvuxAk5VLQAFnVsMHAoC/8RRN 2jJEELEODhwDE9eI+iT4XbUeJyxRLfZnfEcfWKyShzlt52BxI3BF4tim9LNyP5DZ i5MhxEynP282h+E2xRIzc= X-Virus-Scanned: Debian amavisd-new at verdnatura.es Received: from ip1-isp1-algemesi.verdnatura.es ([127.0.0.1]) by localhost (ip1-isp1-algemesi.verdnatura.es [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BOZRCPJ507Tm; Thu, 27 Jul 2023 08:20:59 +0200 (CEST) Received: from webmail.verdnatura.es (kube-worker4.static.verdnatura.es [10.0.2.124]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ip1-isp1-algemesi.verdnatura.es (Postfix) with ESMTPSA id 1022DA0082; Thu, 27 Jul 2023 08:20:58 +0200 (CEST) MIME-Version: 1.0 Date: Thu, 27 Jul 2023 08:20:58 +0200 From: nada To: Proxmox VE user list In-Reply-To: References: Message-ID: <9cdaee916a179c2658aa41689c72e906@verdnatura.es> X-Sender: nada@verdnatura.es Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.111 Adjusted score from AWL reputation of From: address 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 DMARC_PASS -0.1 DMARC pass policy KAM_NUMSUBJECT 0.5 Subject ends in numbers excluding current years SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [PVE-User] PVE 7 - upgrade to ifupdown2 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: Thu, 27 Jul 2023 06:21:08 -0000 hi Alessio yes, you need just install ifupdown2 at ALL nodes and after that you may just try to change some comment of one of yours net via webGUI at node > system > network > after that you'll see diff and just do Apply... NadaMac On 2023-07-26 18:21, Alessio Cecchi via pve-user wrote: > Hi, > we have upgrade a PVE cluster from 5.4 to 6.4 and now to 7.4. Before to > upgrade to PVE 8 I would like to switch to ifupdown2. > What is the right procedure to upgrade to ifupdown2 and the steps to > pay attention to? > Is sufficient to migrate all VM from the node and do "apt install > ifupdown2" one node after another? > Should I update somethings in /etc/network/interfaces (we are using > bond+bridge+VLAN)? > Thanks > -- > Alessio Cecchi > Postmaster @http://www.qboxmail.it > https://www.linkedin.com/in/alessice > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user