qm: update section about audio devices

[pve-docs.git] / pvesdn.adoc

diff --git a/pvesdn.adoc b/pvesdn.adoc
index cb7ee60aa4a1833777be009cd45905a0b4a47069..c1597b82cd30e6492d4190d16fb67400f0364bbb 100644 (file)
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -114,6 +114,9 @@ VNet properties are:
 
 * Tag: The unique VLAN or VXLAN id
 
+* VLAN Aware: Allow to add an extra VLAN tag in the virtual machine or
+  container vNIC configurations or allow the guest OS to manage the VLAN's tag.
+
 * IPv4: an anycast IPv4 address, it will be configured on the underlying bridge
   on each node part of the Zone. It's only useful for `bgp-evpn` routing.
 
@@ -150,7 +153,7 @@ specific VNets VLAN tag, and restrict Virtual Machines to separated zones.
 
 Specific `VLAN` configuration options:
 
-bridge:: Reuse this local VLAN-aware bridge, or OVS interface, already
+bridge:: Reuse this local bridge or OVS switch, already
 configured on *each* local node.
 
 [[pvesdn_zone_plugin_qinq]]
@@ -265,6 +268,12 @@ After applying the configuration through the main SDN web-interface panel,
 the local network configuration is generated locally on each node in
 `/etc/network/interfaces.d/sdn`, and with ifupdown2 reloaded.
 
+You need to add
+----
+source /etc/network/interfaces.d/*
+----
+at the end of /etc/network/interfaces to have the sdn config included
+
 You can monitor the status of local zones and vnets through the main tree.
 
 
@@ -431,7 +440,7 @@ Create a `myvnet2' with customer VLAN-id 100 on the previously created
 
 ----
 id: myvnet2
-zone: qinqzone1
+zone: qinqzone2
 tag: 100
 ----