From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2 1/3] network: remove ifup ifdown as it won't reattach guests
Date: Thu, 2 Jun 2022 11:22:49 +0200 [thread overview]
Message-ID: <20220602092251.1393709-2-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20220602092251.1393709-1-a.lauterer@proxmox.com>
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 <a.lauterer@proxmox.com>
---
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
next prev parent reply other threads:[~2022-06-02 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 9:22 [pve-devel] [PATCH docs v2 0/3] network: update & reword Aaron Lauterer
2022-06-02 9:22 ` Aaron Lauterer [this message]
2022-09-12 16:02 ` [pve-devel] applied: [PATCH docs v2 1/3] network: remove ifup ifdown as it won't reattach guests Thomas Lamprecht
2022-06-02 9:22 ` [pve-devel] [PATCH docs v2 2/3] network: adapt apply config section to PVE 7 Aaron Lauterer
2022-06-02 9:22 ` [pve-devel] [PATCH docs v2 3/3] network: rework introduction for people with less experience Aaron Lauterer
2022-06-27 13:15 ` [pve-devel] [PATCH docs v2 0/3] network: update & reword Aaron Lauterer
2022-09-12 16:02 ` [pve-devel] applied-series: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220602092251.1393709-2-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox