From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH+RFC docs/common 0/3] fix #4847: network: custom naming for network devices
Date: Thu, 27 Jul 2023 12:37:44 +0200 [thread overview]
Message-ID: <20230727103747.106574-1-f.weber@proxmox.com> (raw)
Patch #1 expands the documentation on custom network interface names,
including the usage of systemd.link files to assign custom names to network
interfaces. Patch #2 and #3 are optional and marked as RFC, with the following
reasoning.
Working on patch #1, I noticed that PVE only recognizes interfaces with
certain names (ethN/en*/ib*) as physical NICs which can be configured in the
GUI. This means that users who want to assign custom names and also use the
GUI have to choose names that match these patterns. This seems inconvenient.
Aaron had the idea of adding a pattern `c*` specifically for "custom" names.
So to maybe start a discussion on this idea, this series comes with two
additional RFC patches: Patch #2 changes the documentation from patch #1
accordingly, and patch #3 adds the `c*` pattern.
docs:
Friedrich Weber (2):
fix #4847: network: extend section on interface naming scheme
network: describe and recommend `c*` names for custom interface
pve-network.adoc | 120 +++++++++++++++++++++++++++++++++++++++++------
1 file changed, 105 insertions(+), 15 deletions(-)
common:
Friedrich Weber (1):
network: recognize interfaces matching `c*` as physical NICs
src/PVE/Network.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Summary over all repositories:
2 files changed, 106 insertions(+), 16 deletions(-)
--
murpp v0.4.0
next 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 Friedrich Weber [this message]
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 ` [pve-devel] [RFC docs 2/3] network: describe and recommend `c*` names for custom interface Friedrich Weber
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-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox