From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 1/1] network: update name of pinning tool
Date: Tue, 5 Aug 2025 14:26:58 +0200 [thread overview]
Message-ID: <20250805122701.231702-1-s.hanreich@proxmox.com> (raw)
Has been changed from proxmox-network-interface-pinning to
pve-network-interface-pinning for the initial release, since we do not
include the standalone rust tool for now.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
pve-network.adoc | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/pve-network.adoc b/pve-network.adoc
index 289d6ad..a46ce0e 100644
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -158,8 +158,8 @@ command line. You need to reboot for the changes to take effect.
Overriding network device names
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Using the proxmox-network-interface-pinning Tool
-++++++++++++++++++++++++++++++++++++++++++++++++
+Using the pve-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
@@ -193,29 +193,29 @@ configuration files (see above). The generated names will use the default prefix
`nic`, so the resulting interface names will be `nic1`, `nic2`, ...
----
-proxmox-network-interface-pinning generate
+pve-network-interface-pinning generate
----
You can override the default prefix with the `--prefix` flag:
----
-proxmox-network-interface-pinning generate --prefix myprefix
+pve-network-interface-pinning generate --prefix myprefix
----
It is also possible to pin only a specific interface:
----
-proxmox-network-interface-pinning generate --interface enp1s0
+pve-network-interface-pinning generate --interface enp1s0
----
When pinning a specific interface, you can specify the exact name that the
interface should be pinned to:
----
-proxmox-network-interface-pinning generate --interface enp1s0 --target-name if42
+pve-network-interface-pinning generate --interface enp1s0 --target-name if42
----
-In order to apply the changes made by `proxmox-network-interface-pinning` to the
+In order to apply the changes made by `pve-network-interface-pinning` to the
network configuration, the node needs to be rebooted.
--
2.47.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-08-05 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 12:26 Stefan Hanreich [this message]
2025-08-05 13:35 ` [pve-devel] applied: " 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=20250805122701.231702-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox