all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC docs 2/3] network: describe and recommend `c*` names for custom interface
Date: Thu, 27 Jul 2023 12:37:46 +0200	[thread overview]
Message-ID: <20230727103747.106574-3-f.weber@proxmox.com> (raw)
In-Reply-To: <20230727103747.106574-1-f.weber@proxmox.com>

Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
---
 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





  parent reply	other threads:[~2023-07-27 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27 10:37 [pve-devel] [PATCH+RFC docs/common 0/3] fix #4847: network: custom naming for network devices Friedrich Weber
2023-07-27 10:37 ` [pve-devel] [PATCH docs 1/3] fix #4847: network: extend section on interface naming scheme Friedrich Weber
2023-11-17  9:18   ` [pve-devel] applied: " Thomas Lamprecht
2023-07-27 10:37 ` Friedrich Weber [this message]
2023-07-27 10:37 ` [pve-devel] [RFC common 3/3] network: recognize interfaces matching `c*` as physical NICs Friedrich Weber

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=20230727103747.106574-3-f.weber@proxmox.com \
    --to=f.weber@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal