From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/3] network: adapt apply config section to PVE 7
Date: Mon, 30 May 2022 14:40:13 +0200 [thread overview]
Message-ID: <20220530124014.2477717-3-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20220530124014.2477717-1-a.lauterer@proxmox.com>
ifupdown2 is now installed by default, we can therefore omit the whole
installation part
also mention the CLI variant for users who like to edit the network
config directly or are using some config management tools
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pve-network.adoc | 32 +++++++++-----------------------
1 file changed, 9 insertions(+), 23 deletions(-)
diff --git a/pve-network.adoc b/pve-network.adoc
index a33b90c..0eabb87 100644
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -24,34 +24,20 @@ inaccessible.
Reboot Node to apply
^^^^^^^^^^^^^^^^^^^^
-With the default installed `ifupdown` network managing package you need to
-reboot to commit any pending network changes. Most of the time, the basic {pve}
-network setup is stable and does not change often, so rebooting should not be
-required often.
+One way to apply a new network configuration is to reboot the node.
Reload Network with ifupdown2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-With the optional `ifupdown2` network managing package you also can reload the
-network configuration live, without requiring a reboot.
+With the 'ifupdown2' package (default since {pve} 7), it is possible to apply
+network configuration changes without a reboot. If you change the network
+configuration via the GUI, you can click the 'Apply Configuration' button. Run
+the following command if you make changes directly to the
+`/etc/network/interfaces` file:
-Since {pve} 6.1 you can apply pending network changes over the web-interface,
-using the 'Apply Configuration' button in the 'Network' panel of a node.
-
-To install 'ifupdown2' ensure you have the latest {pve} updates installed, then
-
-WARNING: installing 'ifupdown2' will remove 'ifupdown', but as the removal
-scripts of 'ifupdown' before version '0.8.35+pve1' have a issue where network
-is fully stopped on removal footnote:[Introduced with Debian Buster:
-https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945877] you *must* ensure
-that you have a up to date 'ifupdown' package version.
-
-For the installation itself you can then simply do:
-
- apt install ifupdown2
-
-With that you're all set. You can also switch back to the 'ifupdown' variant at
-any time, if you run into issues.
+----
+ ifreload -a
+----
Naming Conventions
~~~~~~~~~~~~~~~~~~
--
2.30.2
next prev parent reply other threads:[~2022-05-30 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 12:40 [pve-devel] [PATCH docs 0/3] network: update & reword Aaron Lauterer
2022-05-30 12:40 ` [pve-devel] [PATCH docs 1/3] network: remove ifup ifdown as it won't reattach guests Aaron Lauterer
2022-05-30 12:40 ` Aaron Lauterer [this message]
2022-05-30 12:40 ` [pve-devel] [PATCH docs 3/3] network: rework introduction for people with less experience Aaron Lauterer
2022-05-30 12:50 ` [pve-devel] [PATCH docs 0/3] network: update & reword Thomas Lamprecht
2022-05-30 12:53 ` Aaron Lauterer
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=20220530124014.2477717-3-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