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.

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

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.

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