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 1254461

Summary:	Wi-Fi band-locking doesn't work
Product:	Red Hat Enterprise Linux 7	Reporter:	Jirka Klimes <jklimes>
Component:	NetworkManager	Assignee:	Jirka Klimes <jklimes>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	dcbw, jklimes, rkhan, thaller, vbenes, vhumpa
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	NetworkManager-1.0.4-10.el7	Doc Type:	Bug Fix
Doc Text:	Due to a bug in NetworkManager, it was not previously possible to set the Wi-Fi band to the "a" or "bg" values to lock to a specific frequency band. NetworkManager has been fixed, and it now sets the wpa_supplicant's "freq_list" option correctly, which enables proper Wi-Fi band locking.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 11:03:11 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 Jirka Klimes 2015-08-18 08:10:54 UTC

NetworkManager can only use Wi-Fi band "a" or "bg" if the 802-11-wireless.band property is set. It is done via specifying allowed frequences to wpa_supplicant.

It does not work as expected though. NetworkManager sets wpa_supplicant's 'freq_list' option as comma-separated frequences, but wpa_supplicant expects space-separated list.

Comment 1 Jirka Klimes 2015-08-18 08:14:03 UTC

See upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=627571#c11
and branch jk/freq-list-bgo627571 for a fix.

Comment 2 Jirka Klimes 2015-08-21 09:02:37 UTC

Let's put the following commit to RHEL 7.2
c8b5b5e supplicant: wpa_supplicant wants space-separated list in freq_list (bgo #627571)
It fixes the bug. The rest of the upstream branch will get into RHEL when we rebase to NM 1.0.6.

Comment 4 Vitezslav Humpa 2015-10-04 16:07:21 UTC

Verified band locking works by a series of automated test on several different wireless HW devices available.

Comment 5 errata-xmlrpc 2015-11-19 11:03:11 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, 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://rhn.redhat.com/errata/RHSA-2015-2315.html