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.
Bug 2128809 - [RFE] Support 802.1ad VLAN stacking
Summary: [RFE] Support 802.1ad VLAN stacking
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Filip Pokryvka
Jaroslav Klech
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-21 14:40 UTC by Gris Ge
Modified: 2023-05-14 13:21 UTC (History)
13 users (show)

Fixed In Version: NetworkManager-1.41.7-1.el9
Doc Type: Enhancement
Doc Text:
.NetworkManager now supports a new `vlan.protocol` property With this update, the `vlan` interface type now accepts a new `protocol` property. The property type is string. The accepted values are either `802.1Q` (default), or `802.1ad`. The new property specifies which VLAN protocol controls the tag identifier for encapsulation.
Clone Of:
Environment:
Last Closed: 2023-05-09 08:17:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
Test script (916 bytes, application/x-shellscript)
2022-12-02 17:41 UTC, Beniamino Galvani 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-139 0 None None None 2023-01-23 10:06:44 UTC
Red Hat Issue Tracker RHELPLAN-134611 0 None None None 2022-09-21 14:57:41 UTC
Red Hat Product Errata RHBA-2023:2485 0 None None None 2023-05-09 08:17:52 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 1297 0 None merged vlan: add vlan_stacking test 2023-01-23 12:50:16 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1473 0 None merged Add support for VLAN protocol 2022-12-14 10:37:23 UTC

Description Gris Ge 2022-09-21 14:40:03 UTC 
Description of problem:

Request the support of:


ip link add link eth0 eth0.24 type vlan proto 802.1ad id 24
ip link add link eth0.24 eth0.24.371 type vlan proto 802.1Q id 371



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Beniamino Galvani 2022-12-02 17:41:01 UTC 
Created attachment 1929414 [details]
Test script
Comment 15 errata-xmlrpc 2023-05-09 08:17:33 UTC 
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 (NetworkManager bug fix and enhancement update), 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/RHBA-2023:2485
Note You need to log in before you can comment on or make changes to this bug.