From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id E00D11FF165 for ; Thu, 31 Jul 2025 14:17:35 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C1C633A691; Thu, 31 Jul 2025 14:19:02 +0200 (CEST) From: Stefan Hanreich To: pve-devel@lists.proxmox.com Date: Thu, 31 Jul 2025 14:18:25 +0200 Message-ID: <20250731121827.311601-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.195 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 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 documentation for network-interface-pinning 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" It is now possible to use arbitrary prefix names and target names for network interfaces. Update the documentation to reflect this behavior and add some more examples. Signed-off-by: Stefan Hanreich --- pve-network.adoc | 32 +++++++++++++++++++++++++++----- 1 file changed, 27 insertions(+), 5 deletions(-) diff --git a/pve-network.adoc b/pve-network.adoc index 2dec882..1c6b723 100644 --- a/pve-network.adoc +++ b/pve-network.adoc @@ -168,31 +168,53 @@ occurences of the old interface name in the following files: * `/etc/network/interfaces` * `/etc/pve/nodes//host.fw` * `/etc/pve/sdn/controllers.cfg` +* `/etc/pve/sdn/fabrics.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`. +The generated link files are stored in `/usr/local/lib/systemd/network`. For the +configuration files a new file will be generated in the same place with a `.new` +suffix. This way you can inspect the changes made to the configuration by +using diff (or another diff viewer of your choice): -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`, ... +---- +diff -y /etc/network/interfaces /etc/network/interfaces.new +---- + +If you see any problematic changes or want to revert the changes made by the +pinning tool **before rebooting**, simply delete all `.new` files and the +respective link files from `/usr/local/lib/systemd/network`. 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): +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 ---- +You can override the default prefix with the `--prefix` flag: + +---- +proxmox-network-interface-pinning generate --prefix myprefix +---- + It is also possible to pin only a specific interface: ---- proxmox-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 +---- + In order to apply the changes made by `proxmox-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