From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs v2 1/3] network: remove ifup ifdown as it won't reattach guests
Date: Mon, 12 Sep 2022 18:02:16 +0200 [thread overview]
Message-ID: <cb5ea511-490a-b409-5751-99f2b4c946e9@proxmox.com> (raw)
In-Reply-To: <20220602092251.1393709-2-a.lauterer@proxmox.com>
Am 02/06/2022 um 11:22 schrieb Aaron Lauterer:
> 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'.
>
all true, but in the light of the pitfalls it is actually better to actively
warn, not just remove. Done so in a follow-up.
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
> pve-network.adoc | 3 ---
> 1 file changed, 3 deletions(-)
>
>
applied, thanks!
next prev parent reply other threads:[~2022-09-12 16:02 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 ` [pve-devel] [PATCH docs v2 1/3] network: remove ifup ifdown as it won't reattach guests Aaron Lauterer
2022-09-12 16:02 ` Thomas Lamprecht [this message]
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=cb5ea511-490a-b409-5751-99f2b4c946e9@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.