Bug 1892700

Summary:	Update wireless regulatory database
Product:	Red Hat Enterprise Linux 8	Reporter:	Quentin Haas <quent.haas>
Component:	crda	Assignee:	Jarod Wilson <jarod>
Status:	CLOSED ERRATA	QA Contact:	Ken Benoit <kbenoit>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	hwkernel-mgr, jarod, rvr
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.4
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	crda-3.18_2020.04.29-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-18 15:05:27 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 Quentin Haas 2020-10-29 13:28:42 UTC

Description of problem:
The wireless regulatory database (wireless-regdb[1]) provided by the crda package in RHEL8[2] is dated May 2018.  New spectrum in the US region became available with the April 2020 update upstream[3].  Users of Fedora 33[4] and Debian Stable[5], which which have this updated regulatory information can now use additional spectrum with supported hardware that are unavailable to those using outdated regulatory information.  Please consider updating the database so RHEL8 users can use the spectrum allotted to US users by the FCC. 

Version-Release number of selected component (if applicable):
crda 3.18_2018.05.31

How reproducible:
everytime

Steps to Reproduce:
1. For US based users, view the list of supported spectrum with `iw reg get`
2. Compare to the current regulatory state[3]

Actual results:
Supported spectrum differs from current regulatory state

Expected results:
Supported spectrum matches current regulatory state


[1]: https://wireless.wiki.kernel.org/en/developers/regulatory/wireless-regdb#releases_of_wireless-regdb
[2]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/managing-wi-fi-connections_configuring-and-managing-networking#Setting_the_Wireless_Regulatory_Domain_managing-wi-fi-connections
[3]: https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=5099e0759d1a93212c9bff088d9c16e5688f7cc3
[4]: https://src.fedoraproject.org/rpms/wireless-regdb
[5]: https://packages.debian.org/buster-backports/wireless-regdb

Comment 10 Ken Benoit 2020-12-10 17:04:54 UTC

Given that pretty much everything is self-managed now for wireless regulations on cards, I at least verified that the new version of crda (crda-3.18_2020.04.29-1.el8) installed correctly on RHEL-8.4.0-20201203.n.0. I ran testing against 10 different cards using automated testing as well as manually running iperf3 testing for an hour on 2 different cards to ensure there were no issues. I also confirmed that performing "iw reg get" still gets back the regulatory information correctly. Setting does nothing, but that's to be expected on self-managed hardware. Verifying as SanityOnly.

Comment 12 errata-xmlrpc 2021-05-18 15:05:27 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 (crda 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/RHEA-2021:1673