[pve-devel] [PATCH docu] Fix #545: Update allowed network device names
Dominic Jäger
d.jaeger at proxmox.com
Wed May 15 11:49:31 CEST 2019
Signed-off-by: Dominic Jäger <d.jaeger at proxmox.com>
---
pve-network.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/pve-network.adoc b/pve-network.adoc
index 9e0c439..2a78dd1 100644
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -32,12 +32,12 @@ We currently use the following naming conventions for device names:
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.
-* Bridge names: vmbr[N], where 0 ≤ N ≤ 4094 (`vmbr0` - `vmbr4094`)
+* Bridge names: vmbr[w], where w is a "word" character (`vmbr0`, `vmbr123`, `vmbr_test`, ...)
-* Bonds: bond[N], where 0 ≤ N (`bond0`, `bond1`, ...)
+* Bonds: bond[w], where w is a "word" character (`bond0`, `bond123`, `bond_test`, ...)
* VLANs: Simply add the VLAN number to the device name,
- separated by a period (`eno1.50`, `bond1.30`)
+ separated by a period (`eno1.50`, `bond1.30`, ...)
This makes it easier to debug networks problems, because the device
name implies the device type.
--
2.11.0
More information about the pve-devel
mailing list