From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs v3 1/1] network: add documentation for proxmox-network-interface-pinning
Date: Wed, 16 Jul 2025 18:39:11 +0200 [thread overview]
Message-ID: <20250716163911.406995-10-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20250716163911.406995-1-s.hanreich@proxmox.com>
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
pve-network.adoc | 42 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
diff --git a/pve-network.adoc b/pve-network.adoc
index 55c796b..48f3d5b 100644
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -158,6 +158,48 @@ command line. You need to reboot for the changes to take effect.
Overriding network device names
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Using the proxmox-network-interface-pinning tool
+++++++++++++++++++++++++++++++++++++++++++++++++
+
+Proxmox VE provides a tool for automatically generating .link files for
+overriding the name of network devices. It also automatically replaces the
+occurences of the old interface name in the following files:
+
+* `/etc/network/interfaces`
+* `/etc/pve/nodes/<nodename>/host.fw`
+* `/etc/pve/sdn/controllers.cfg`
+
+NOTE: Since the generated mapping is local to the node it is generated on,
+interface names contained in the Firewall Datacenter configuration
+(`/etc/pve/firewall/cluster.fw`) are **not** automatically updated.
+
+The generated link files are stored in `/usr/local/lib/systemd/network`.
+
+It is currently only possible to generate names with the prefix `nic`, since
+otherwise the interfaces would not get recognized as a physical interface. When
+auto-generating new interface names, the tool will use `nic0`, `nic1`, ...
+
+The following command will generate a .link file for all physical network
+interfaces that do not yet have a .link file and update selected Proxmox VE
+configuration files (see above):
+
+----
+proxmox-network-interface-pinning generate
+----
+
+It is also possible to pin only a specific interface:
+
+----
+proxmox-network-interface-pinning generate --nic enp1s0
+----
+
+In order to apply the changes made by `proxmox-network-interface-pinning` to the
+network configuration, the node needs to be rebooted.
+
+
+Manual method
++++++++++++++
+
You can manually assign a name to a particular network device using a custom
https://manpages.debian.org/stable/udev/systemd.link.5.en.html[systemd.link
file]. This overrides the name that would be assigned according to the latest
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-16 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 16:39 [pve-devel] [RFC common/docs/firewall/manager/network/proxmox{-ve-rs, -firewall} v3 0/9] NIC renaming mitigations 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 ` Stefan Hanreich [this message]
2025-07-16 17:49 ` [pve-devel] applied-series: [RFC common/docs/firewall/manager/network/proxmox{-ve-rs, -firewall} v3 0/9] NIC renaming mitigations 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=20250716163911.406995-10-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox