From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id CE9D78620 for ; Thu, 27 Jul 2023 12:39:31 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id AFE9AA1C5 for ; Thu, 27 Jul 2023 12:39:01 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Thu, 27 Jul 2023 12:39:01 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id BE49E40EC3 for ; Thu, 27 Jul 2023 12:39:00 +0200 (CEST) From: Friedrich Weber To: pve-devel@lists.proxmox.com Date: Thu, 27 Jul 2023 12:37:46 +0200 Message-Id: <20230727103747.106574-3-f.weber@proxmox.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20230727103747.106574-1-f.weber@proxmox.com> References: <20230727103747.106574-1-f.weber@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -2.680 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_SOMETLD_ARE_BAD_TLD 5 .bar, .beauty, .buzz, .cam, .casa, .cfd, .club, .date, .guru, .link, .live, .monster, .online, .press, .pw, .quest, .rest, .sbs, .shop, .stream, .top, .trade, .wiki, .work, .xyz TLD abuse SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [RFC docs 2/3] network: describe and recommend `c*` names for custom interface 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: , X-List-Received-Date: Thu, 27 Jul 2023 10:39:31 -0000 Signed-off-by: Friedrich Weber --- pve-network.adoc | 20 +++++++++----------- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/pve-network.adoc b/pve-network.adoc index b2202cc..bd6a15d 100644 --- a/pve-network.adoc +++ b/pve-network.adoc @@ -71,6 +71,9 @@ We currently use the following naming conventions for device names: * Ethernet devices: `en*`, systemd network interface names. This naming scheme is used for new {pve} installations since version 5.0. +* Ethernet devices: `c*`, intended for user-defined **c**ustom interface names +(see xref:network_override_device_names[below]). + * Ethernet devices: `eth[N]`, where 0 ≤ N (`eth0`, `eth1`, ...) This naming scheme is used for {pve} hosts which were installed before the 5.0 release. When upgrading to 5.0, the names are kept as-is. @@ -173,28 +176,23 @@ to match the device's MAC address using the `MACAddress` option, as it is unlikely to change. Then, you can assign a name using the `Name` option in the `[Link]` section. -For example, to assign the name `enwan0` to the device with MAC address -`aa:bb:cc:dd:ee:ff`, create a file `/etc/systemd/network/10-enwan0.link` with -the following contents: +For example, to assign the name `cwan0` to the device with MAC address +`aa:bb:cc:dd:ee:ff`, create a file `/etc/systemd/network/10-cwan0.link` with ---- [Match] MACAddress=aa:bb:cc:dd:ee:ff [Link] -Name=enwan0 +Name=cwan0 ---- Do not forget to adjust `/etc/network/interfaces` to use the new name. You need to reboot the node for the change to take effect. -NOTE: It is recommended to assign a name starting with `en` or `eth` so that -{pve} recognizes the interface as a physical network device which can then be -configured via the GUI. Also, you should ensure that the name will not clash -with other interface names in the future. One possibility is to assign a name -that does not match any name pattern that systemd uses for network interfaces -(xref:systemd_network_interface_names[see above]), such as `enwan0` in the -example above. +NOTE: It is recommended to assign a name starting with `c` (for **c**ustom) so +that {pve} recognizes the interface as a physical network device which can then +be configured via the GUI. For more information on link files, see the https://manpages.debian.org/stable/udev/systemd.link.5.en.html[systemd.link(5) -- 2.39.2