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 0A54C1FF16B for ; Tue, 12 Aug 2025 14:56:29 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 40A03D28E; Tue, 12 Aug 2025 14:58:06 +0200 (CEST) From: Christoph Heiss To: pbs-devel@lists.proxmox.com Date: Tue, 12 Aug 2025 14:57:17 +0200 Message-ID: <20250812125719.1301475-2-c.heiss@proxmox.com> X-Mailer: git-send-email 2.50.1 In-Reply-To: <20250812125719.1301475-1-c.heiss@proxmox.com> References: <20250812125719.1301475-1-c.heiss@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1755003452142 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.035 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 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. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [interfaces.new] Subject: [pbs-devel] [PATCH proxmox-backup 1/2] docs: network-management: use correct syntax for code-blocks X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" Probably copied over from the asciidoc documentation for PVE, which uses a different syntax. Fixes: 03fc1efc ("docs: add documentation for proxmox-network-interface-pinning") Signed-off-by: Christoph Heiss --- docs/network-management.rst | 55 ++++++++++++++++++------------------- 1 file changed, 27 insertions(+), 28 deletions(-) diff --git a/docs/network-management.rst b/docs/network-management.rst index 492becdf..f1dc4cc5 100644 --- a/docs/network-management.rst +++ b/docs/network-management.rst @@ -106,49 +106,48 @@ When upgrading kernels, adding PCIe devices or updating your BIOS, automatically generated network interface names can change. To alleviate this issues, Proxmox Backup Server 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 `/etc/network/interfaces`. +occurrences of the old interface name in ``/etc/network/interfaces``. -The generated link files are stored in `/usr/local/lib/systemd/network`. For the -interfaces file 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): +The generated link files are stored in ``/usr/local/lib/systemd/network``. For +the interfaces file 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): ----- -diff -y /etc/network/interfaces /etc/network/interfaces.new ----- +.. code-block:: console + + 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`. +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 +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). The generated names will use the default prefix -`nic`, so the resulting interface names will be `nic1`, `nic2`, ... +``nic``, so the resulting interface names will be ``nic1``, ``nic2``, ... ----- -proxmox-network-interface-pinning generate ----- +.. code-block:: console -You can override the default prefix with the `--prefix` flag: + proxmox-network-interface-pinning generate ----- -proxmox-network-interface-pinning generate --prefix myprefix ----- +You can override the default prefix with the ``--prefix`` flag: + +.. code-block:: console + + proxmox-network-interface-pinning generate --prefix myprefix It is also possible to pin only a specific interface: ----- -proxmox-network-interface-pinning generate --interface enp1s0 ----- +.. code-block:: console + + 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 ----- +.. code-block:: console -In order to apply the changes made by `proxmox-network-interface-pinning` to the -network configuration, the host needs to be rebooted. + 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 host needs to be rebooted. -- 2.50.1 _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel