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 9D1ED73C11 for ; Mon, 30 May 2022 14:40:46 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 940EF2D5C0 for ; Mon, 30 May 2022 14:40:16 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (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 id BEE3F2D5A6 for ; Mon, 30 May 2022 14:40:15 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 8057643789 for ; Mon, 30 May 2022 14:40:15 +0200 (CEST) From: Aaron Lauterer To: pve-devel@lists.proxmox.com Date: Mon, 30 May 2022 14:40:12 +0200 Message-Id: <20220530124014.2477717-2-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20220530124014.2477717-1-a.lauterer@proxmox.com> References: <20220530124014.2477717-1-a.lauterer@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.006 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: [pve-devel] [PATCH docs 1/3] network: remove ifup ifdown as it won't reattach guests X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2022 12:40:46 -0000 Mentioning 'ifup' and 'ifdown' can lead to users running into situations where they take down one interface, for example an vmbrX. In this situation the connection to the guests will be lost and not reestablished automatically if the interface is brought up again with 'ifup'. The better way to apply network changes is to run 'ifreload -a'. Signed-off-by: Aaron Lauterer --- pve-network.adoc | 3 --- 1 file changed, 3 deletions(-) diff --git a/pve-network.adoc b/pve-network.adoc index c5e9a17..a33b90c 100644 --- a/pve-network.adoc +++ b/pve-network.adoc @@ -12,9 +12,6 @@ complete format description. All {pve} tools try hard to keep direct user modifications, but using the GUI is still preferable, because it protects you from errors. -Once the network is configured, you can use the Debian traditional tools `ifup` -and `ifdown` commands to bring interfaces up and down. - Apply Network Changes ~~~~~~~~~~~~~~~~~~~~~ -- 2.30.2