proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-06-14 18:27:32 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

network: update specification for bridge names

Browse Source 
Reviewed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
This commit is contained in:
Stefan Hanreich 2024-04-12 10:07:33 +02:00 committed by Thomas Lamprecht
parent a3806d641c
commit 0500f140bf
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
pve-network.adoc
View File

@ -13,11 +13,11 @@ page contains the complete format description. All {pve} tools try hard to keep
direct user modifications, but using the GUI is still preferable, because it direct user modifications, but using the GUI is still preferable, because it
protects you from errors. protects you from errors.
A 'vmbr' interface is needed to connect guests to the underlying physical A Linux bridge interface (commonly called 'vmbrX') is needed to connect guests
network. They are a Linux bridge which can be thought of as a virtual switch to the underlying physical network. It can be thought of as a virtual switch
to which the guests and physical interfaces are connected to. This section which the guests and physical interfaces are connected to. This section provides
provides some examples on how the network can be set up to accomodate different some examples on how the network can be set up to accomodate different use cases
use cases like redundancy with a xref:sysadmin_network_bond['bond'], like redundancy with a xref:sysadmin_network_bond['bond'],
xref:sysadmin_network_vlan['vlans'] or xref:sysadmin_network_vlan['vlans'] or
xref:sysadmin_network_routed['routed'] and xref:sysadmin_network_routed['routed'] and
xref:sysadmin_network_masquerading['NAT'] setups. xref:sysadmin_network_masquerading['NAT'] setups.
@ -75,7 +75,9 @@ We currently use the following naming conventions for device names:
scheme is used for {pve} hosts which were installed before the 5.0 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. release. When upgrading to 5.0, the names are kept as-is.
* Bridge names: `vmbr[N]`, where 0 ≤ N ≤ 4094 (`vmbr0` - `vmbr4094`) * Bridge names: Commonly `vmbr[N]`, where 0 ≤ N ≤ 4094 (`vmbr0` - `vmbr4094`),
but you can use any alphanumeric string that starts with a character and is at
most 10 characters long.
* Bonds: `bond[N]`, where 0 ≤ N (`bond0`, `bond1`, ...) * Bonds: `bond[N]`, where 0 ≤ N (`bond0`, `bond1`, ...)