man,NEWS: mention that all previously assigned VLAN IDs are cleared

Addresses https://github.com/systemd/systemd/pull/29987#issuecomment-1863934902.
This commit is contained in:
Yu Watanabe
2023-12-20 19:12:34 +09:00
parent b9e6e92510
commit 03a46b5eca
2 changed files with 17 additions and 4 deletions

6
NEWS
View File

@@ -4,6 +4,12 @@ CHANGES WITH 256 in spe:
Announcements of Future Feature Removals and Incompatible Changes:
* Previously, systemd-networkd did not explicitly remove any bridge VLAN
IDs assigned on bridge master and ports. Since v256, if a .network
file for an interface has at least one valid settings in [BridgeVLAN]
section, then all assigned VLAN IDs on the interface that are not
configured in the .network file are removed.
CHANGES WITH 255:
Announcements of Future Feature Removals and Incompatible Changes:

View File

@@ -5865,10 +5865,17 @@ ServerAddress=192.168.0.1/24</programlisting>
<refsect1>
<title>[BridgeVLAN] Section Options</title>
<para>The [BridgeVLAN] section manages the VLAN ID configuration of a bridge port and accepts the
following keys. Specify several [BridgeVLAN] sections to configure several VLAN entries. The
<varname>VLANFiltering=</varname> option has to be enabled, see the [Bridge] section in
<citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<para>
The [BridgeVLAN] section manages the VLAN ID configurations of a bridge master or port, and accepts the
following keys. To make the settings in this section take an effect,
<varname>VLANFiltering=</varname> option has to be enabled on the bridge master, see the [Bridge]
section in
<citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
If at least one valid settings specified in this section in a .network file for an interface, all
assigned VLAN IDs on the interface that are not configured in the .network file will be removed. If
VLAN IDs on an interface need to be managed by other tools, then the settings in this section cannot
be used in the matching .network file.
</para>
<variablelist class='network-directives'>
<varlistentry>