From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied-series: [RFC common/docs/firewall/manager/network/proxmox{-ve-rs, -firewall} v3 0/9] NIC renaming mitigations
Date: Wed, 16 Jul 2025 19:49:51 +0200 [thread overview]
Message-ID: <660a9ecf-8d60-4ec9-8963-f5e44cf694b1@proxmox.com> (raw)
In-Reply-To: <20250716163911.406995-1-s.hanreich@proxmox.com>
Am 16.07.25 um 18:39 schrieb Stefan Hanreich:
> This patch series contains the following features:
> * transparent altname support for {pve, proxmox}-firewall and pve-network
> * proxmox-network-interface-pinning tool for pinning NIC names
>
> Both are improvements aimed at mitigating the fallout caused from changing
> network interface names.
>
> For more information on the pinning tool, see the respective commit that
> explains the usage - a short tl;dr:
>
> * Pin network interfaces via proxmox-network-interface-pinning generate
> * reboot to apply the changes to the network configuration
>
> I also introduce two new one-shot services, that are executed on boot, for
> applying pending network configuration changes.
applied series, thanks!
FWIW, I made some follow-up commits in pve-manager, would be great if you
can take another look to verify I did not mess anything up.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-16 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 16:39 [pve-devel] " Stefan Hanreich
2025-07-16 16:39 ` [pve-devel] [PATCH pve-common v3 1/2] network: add ip link and altname helpers Stefan Hanreich
2025-07-16 16:39 ` [pve-devel] [PATCH pve-common v3 2/2] network: add nic prefix to physical nic regex Stefan Hanreich
2025-07-16 16:39 ` [pve-devel] [PATCH proxmox-ve-rs v3 1/1] config: ip link struct Stefan Hanreich
2025-07-16 16:39 ` [pve-devel] [PATCH proxmox-firewall v3 1/1] firewall: add altname support for firewall rules Stefan Hanreich
2025-07-16 16:39 ` [pve-devel] [PATCH pve-firewall v3 1/1] firewall: add altname support Stefan Hanreich
2025-07-16 16:39 ` [pve-devel] [PATCH pve-network v3 1/1] controllers: isis: " Stefan Hanreich
2025-07-16 16:39 ` [pve-devel] [PATCH pve-manager v3 1/2] cli: add proxmox-network-interface-pinning tool Stefan Hanreich
2025-07-16 16:39 ` [pve-devel] [PATCH pve-manager v3 2/2] services: add pvesdncommit and pvefirewallcommit Stefan Hanreich
2025-07-16 16:39 ` [pve-devel] [PATCH pve-docs v3 1/1] network: add documentation for proxmox-network-interface-pinning Stefan Hanreich
2025-07-16 17:49 ` Thomas Lamprecht [this message]
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=660a9ecf-8d60-4ec9-8963-f5e44cf694b1@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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.