Skip to content

Commit c512e4e

Browse files
committed
add note on how to open vlans on uplink
1 parent 8d031fd commit c512e4e

1 file changed

Lines changed: 13 additions & 1 deletion

File tree

‎source/adminguide/networking/multi_vlan_trunk_nics.rst‎

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,19 @@ only the guest taps.
159159
already known and bounded by the zone's own configuration, and
160160
``specifyvlan=true`` (letting a network request a VLAN outside that
161161
range) is already restricted to root administrators, so this is a
162-
one-time, predictable step.
162+
one-time, predictable step. On each host, against the guest bridge's
163+
uplink interface (or its bond, if the uplink is bonded):
164+
165+
.. code:: bash
166+
167+
bridge vlan add dev <guest_uplink_interface> vid <start_vlan>-<end_vlan>
168+
bridge vlan show dev <guest_uplink_interface>
169+
170+
This takes effect immediately but is not persistent. Also save this
171+
VLAN membership in the host's own network configuration tool so it
172+
survives a reboot (for example ``bridge-port.vlans`` under
173+
NetworkManager, or a ``[BridgeVLAN]`` section under
174+
systemd-networkd).
163175

164176
- Whenever ``specifyvlan=true`` is used to put a network on a VLAN
165177
outside the zone's normal dynamic range, also open that specific VLAN

0 commit comments

Comments
 (0)