bump version to 5.4-2

[pve-docs.git] / pve-network.adoc

diff --git a/pve-network.adoc b/pve-network.adoc
index 198f2d1681b4888a6d4a81bb76a37e6ba6b3aeb9..9e0c439c2fba62df099a0830d7614b2897a08344 100644 (file)
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -102,6 +102,7 @@ virtual networks.
 Default Configuration using a Bridge
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Default Configuration using a Bridge
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

+[thumbnail="default-network-setup-bridge.svg"]

 Bridges are like physical network switches implemented in software.
 All VMs can share a single bridge, or you can create multiple bridges to 
 separate network domains. Each host can have up to 4094 bridges.
 Bridges are like physical network switches implemented in software.
 All VMs can share a single bridge, or you can create multiple bridges to 
 separate network domains. Each host can have up to 4094 bridges.


@@ -138,7 +139,7 @@ Most hosting providers do not support the above setup. For security
 reasons, they disable networking as soon as they detect multiple MAC
 addresses on a single interface.
 
 reasons, they disable networking as soon as they detect multiple MAC
 addresses on a single interface.
 

-TIP: Some providers allows you to register additional MACs on there
+TIP: Some providers allows you to register additional MACs on their

 management interface. This avoids the problem, but is clumsy to
 configure because you need to register a MAC for each of your VMs.
 
 management interface. This avoids the problem, but is clumsy to
 configure because you need to register a MAC for each of your VMs.
 


@@ -146,6 +147,7 @@ You can avoid the problem by ``routing'' all traffic via a single
 interface. This makes sure that all network packets use the same MAC
 address.
 
 interface. This makes sure that all network packets use the same MAC
 address.
 

+[thumbnail="default-network-setup-routed.svg"]

 A common scenario is that you have a public IP (assume `198.51.100.5`
 for this example), and an additional IP block for your VMs
 (`203.0.113.16/29`). We recommend the following setup for such
 A common scenario is that you have a public IP (assume `198.51.100.5`
 for this example), and an additional IP block for your VMs
 (`203.0.113.16/29`). We recommend the following setup for such


@@ -314,6 +316,7 @@ iface vmbr0 inet static
 ----
 
 
 ----
 
 

+[thumbnail="default-network-setup-bond.svg"]

 Another possibility it to use the bond directly as bridge port.
 This can be used to make the guest network fault-tolerant.
 
 Another possibility it to use the bond directly as bridge port.
 This can be used to make the guest network fault-tolerant.
 


@@ -399,12 +402,8 @@ abstraction layers between itself and the physical NIC.
 For example, in a default configuration where you want to place
 the host management address on a separate VLAN.
 
 For example, in a default configuration where you want to place
 the host management address on a separate VLAN.
 

-NOTE: In the examples we use the VLAN at bridge level to ensure the correct
-function of VLAN 5 in the guest network, but in combination with VLAN anwareness
-bridge this it will not work for guest network VLAN 5.
-The downside of this setup is more CPU usage.

 
 

-.Example: Use VLAN 5 for the {pve} management IP
+.Example: Use VLAN 5 for the {pve} management IP with traditional Linux bridge

 ----
 auto lo
 iface lo inet loopback
 ----
 auto lo
 iface lo inet loopback


@@ -430,10 +429,32 @@ iface vmbr0 inet manual
 
 ----
 
 
 ----
 

+.Example: Use VLAN 5 for the {pve} management IP with VLAN aware Linux bridge
+----
+auto lo
+iface lo inet loopback
+
+iface eno1 inet manual
+
+
+auto vmbr0.5
+iface vmbr0.5 inet static
+        address  10.10.10.2
+        netmask  255.255.255.0
+        gateway  10.10.10.1
+
+auto vmbr0
+iface vmbr0 inet manual
+        bridge_ports eno1
+        bridge_stp off
+        bridge_fd 0
+        bridge_vlan_aware yes
+----
+

 The next example is the same setup but a bond is used to
 make this network fail-safe.
 
 The next example is the same setup but a bond is used to
 make this network fail-safe.
 

-.Example: Use VLAN 5 with bond0 for the {pve} management IP
+.Example: Use VLAN 5 with bond0 for the {pve} management IP with traditional Linux bridge

 ----
 auto lo
 iface lo inet loopback
 ----
 auto lo
 iface lo inet loopback