Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 2180795

Summary:	[RFE] Allow configuration of bridge.vlan-default-pvid
Product:	Red Hat Enterprise Linux 9	Reporter:	Petr Horáček <phoracek>
Component:	nmstate	Assignee:	Gris Ge <fge>
Status:	CLOSED ERRATA	QA Contact:	Mingyu Shi <mshi>
Severity:	unspecified	Docs Contact:	Jaroslav Klech <jklech>
Priority:	unspecified
Version:	9.2	CC:	ferferna, fge, jiji, jishi, jklech, network-qe, sfaye, till
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nmstate-2.2.12-1.el9	Doc Type:	Enhancement
Doc Text:	.`nmstate` now supports the `bridge.vlan-default-pvid` NetworkManager configuration option With this update, you can use the `nmstate` framework to configure the `bridge.vlan-default-pvid` NetworkManager configuration option. By using this option, you can set the default port VLAN identifier (PVID) for untagged traffic on a bridge interface that supports VLANs, when you use Linux bridge VLAN filtering. To achieve this result, use the following YAML configuration: ---- interfaces: - name: linux-br0 type: linux-bridge state: up bridge: options: vlan-default-pvid: 5 port: - name: eth1 stp-hairpin-mode: false stp-path-cost: 100 stp-priority: 32 vlan: mode: access tag: 100 ---- Note that the default value of `bridge.vlan-default-pvid` is 1. When set to 0 with VLAN filtering enabled, the untagged traffic is dropped.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-07 08:24:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Horáček 2023-03-22 10:43:20 UTC

Description of problem:
The underlying OS assigns the default VLAN 1 to a newly created bridge and every port attached to it. That can be an unexpected issue when attaching veth pairs to a bridge, marking then with a VLAN tag 100, but then seeing traffic from both VLAN 1 and 100 on the other end of the veth. Providing a way to set bridge.vlan-default-pvid on the bridge would allow administrators to disable this default behavior or set a different ID.

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


How reproducible:
Always

Steps to Reproduce:
1. Create a bridge using nmstate, setting bridge.vlan-default-pvid to None
2. Attach a veth to it

Actual results:
This attribute does not exist

Expected results:
This should be supported and lead into no VLAN assigned to the veth port


Additional info:

Comment 4 Mingyu Shi 2023-06-29 10:16:37 UTC

Verified with:
nmstate-2.2.12-2.el9.x86_64
nispor-1.2.10-1.el9.x86_64
NetworkManager-1.43.10-1.el9.x86_64
DISTRO=RHEL-9.3.0-20230628.0

Comment 8 errata-xmlrpc 2023-11-07 08:24:02 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 (nmstate 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:6323