From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 49F411FF16F for ; Tue, 5 Aug 2025 14:26:10 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EBEA0E4F4; Tue, 5 Aug 2025 14:27:39 +0200 (CEST) From: Stefan Hanreich To: pve-devel@lists.proxmox.com Date: Tue, 5 Aug 2025 14:26:58 +0200 Message-ID: <20250805122701.231702-1-s.hanreich@proxmox.com> X-Mailer: git-send-email 2.47.2 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.191 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: [pve-devel] [PATCH pve-docs 1/1] network: update name of pinning tool X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" 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 --- 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