RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

VLAN ID 4095 is not a valid ID.
A user configuring it, will not succeed.

That was aimed to be fixed by https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8715d61437060cacc68c156b1c8ed7bbce4b0a78 . This change, caused NM to reject VLAN ID 4095, but also failed to load existing connections on disk -- but that is no problem, because such connections were never functional!!


However, the fix was wrong, so it doesn't actually reject the 4095.
This got now fixed by https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=159cd4836fb32f3a6ecefa6fc4dcc114892ce32a


The fix is important, because otherwise a user can configure ID 4095 which triggers an assertion in NetworkManager.

Reproducer:


just create a connection with VLAN ID 4095


$ nmcli connection add type vlan con-name t-vlan autoconnect no id 4095 dev enp0s25



correct result:
Error: Failed to add 't-vlan' connection: vlan.id: the vlan id must be in range 0-4094 but is 4095

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.

https://access.redhat.com/errata/RHSA-2017:2299