From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC common/firewall/manager/network/proxmox{-ve-rs, -firewall} v2 0/8] NIC renaming mitigations
Date: Wed, 16 Jul 2025 17:18:07 +0200 [thread overview]
Message-ID: <20250716151815.348161-1-s.hanreich@proxmox.com> (raw)
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.
Changes from RFC:
* renamed pin -> generate
* removed unpinning feature (will be implemented in a follow-up)
* configuration now gets generated into pending files, instead of directly
rewriting configuration
* created SDN and FW pendants to pvenetcommit for auto-comitting changes on
reboot
pve-common:
Stefan Hanreich (2):
network: add ip link and altname helpers
network: add nic prefix to physical nic regex
src/PVE/Network.pm | 47 +++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 46 insertions(+), 1 deletion(-)
proxmox-ve-rs:
Stefan Hanreich (1):
config: ip link struct
proxmox-ve-config/src/host/mod.rs | 1 +
proxmox-ve-config/src/host/network.rs | 35 +++++++++++++++++++++++++++
2 files changed, 36 insertions(+)
create mode 100644 proxmox-ve-config/src/host/network.rs
proxmox-firewall:
Stefan Hanreich (1):
firewall: add altname support for firewall rules
proxmox-firewall/src/config.rs | 29 +++++++++++++++++++++
proxmox-firewall/src/rule.rs | 6 ++++-
proxmox-firewall/tests/integration_tests.rs | 7 +++++
3 files changed, 41 insertions(+), 1 deletion(-)
pve-firewall:
Stefan Hanreich (1):
firewall: add altname support
src/PVE/Firewall.pm | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
pve-network:
Stefan Hanreich (1):
controllers: isis: add altname support
src/PVE/Network/SDN/Controllers/IsisPlugin.pm | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
pve-manager:
Stefan Hanreich (2):
cli: add proxmox-network-interface-pinning tool
services: add pvesdncommit and pvefirewallcommit
PVE/CLI/Makefile | 1 +
PVE/CLI/proxmox_network_interface_pinning.pm | 396 +++++++++++++++++++
bin/Makefile | 21 +-
bin/proxmox-network-interface-pinning | 8 +
bin/pvefirewallcommit | 14 +
bin/pvesdncommit | 14 +
debian/postinst | 2 +-
services/Makefile | 4 +-
services/pvefirewallcommit.service | 13 +
services/pvesdncommit.service | 13 +
10 files changed, 483 insertions(+), 3 deletions(-)
create mode 100644 PVE/CLI/proxmox_network_interface_pinning.pm
create mode 100644 bin/proxmox-network-interface-pinning
create mode 100644 bin/pvefirewallcommit
create mode 100644 bin/pvesdncommit
create mode 100644 services/pvefirewallcommit.service
create mode 100644 services/pvesdncommit.service
Summary over all repositories:
18 files changed, 615 insertions(+), 8 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-07-16 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 15:18 Stefan Hanreich [this message]
2025-07-16 15:18 ` [pve-devel] [PATCH pve-common v2 1/2] network: add ip link and altname helpers Stefan Hanreich
2025-07-16 15:18 ` [pve-devel] [PATCH pve-common v2 2/2] network: add nic prefix to physical nic regex Stefan Hanreich
2025-07-16 15:18 ` [pve-devel] [PATCH proxmox-ve-rs v2 1/1] config: ip link struct Stefan Hanreich
2025-07-16 15:18 ` [pve-devel] [PATCH proxmox-firewall v2 1/1] firewall: add altname support for firewall rules Stefan Hanreich
2025-07-16 15:18 ` [pve-devel] [PATCH pve-firewall v2 1/1] firewall: add altname support Stefan Hanreich
2025-07-16 15:18 ` [pve-devel] [PATCH pve-network v2 1/1] controllers: isis: " Stefan Hanreich
2025-07-16 15:18 ` [pve-devel] [PATCH pve-manager v2 1/2] cli: add proxmox-network-interface-pinning tool Stefan Hanreich
2025-07-16 15:18 ` [pve-devel] [PATCH pve-manager v2 2/2] services: add pvesdncommit and pvefirewallcommit Stefan Hanreich
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=20250716151815.348161-1-s.hanreich@proxmox.com \
--to=s.hanreich@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.