Description of problem:
When a new VLAN connection is created the default value for VLAN flags
is 0, and then the REORDER_HDR=0 variable is added to the ifcfg file;
but the setting is ignored and the device is created with the
REORDER_HDR flag set.
So the first problem is that we ignore the setting. The second problem
is that when NM will start honoring the setting, all the previously
created connections will not work the same because they won't have the
REORDER_HDR flag. We need to find a way to properly deal with the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
# nmcli connection add type vlan con-name vlan123 ifname vlan123 dev ens3 id 123 ip4 18.104.22.168/32
# nmcli c show vlan123 | grep vlan.flags
vlan.flags: 0 (NONE)
# ip -d l show vlan123
21: vlan123@ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT
link/ether 52:51:00:23:22:d7 brd ff:ff:ff:ff:ff:ff promiscuity 0
vlan protocol 802.1Q id 123 <REORDER_HDR> addrgenmode none
The REORDER_HDR flag in vlan flags is now honored. Newly created connections will have the flag set to REORDER_HDR, which is the default for manually created VLANs. To retain backwards compatibility, the REORDER_HDR variable in ifcfg files is now deprecated (and ignored) in favor of VLAN_FLAGS=[NO_REORDER_HDR].
REORDER_HDR can now be correctly set to true (via REORDER_HDR=yes/no VLAN_FLAGS=NO_REORDER_HDR flag) in ifcfg file or removed (via REORDER_HDR=no/VLAN_FLAGS=NO_REORDER_HDR flag) in ifcfg file. It can be set via nmcli option vlan.flags, too.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.