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 1743730 - don't enable FT-PSK in supplicant, if driver does not support it
Summary: don't enable FT-PSK in supplicant, if driver does not support it
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: 8.0
Assignee: Thomas Haller
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-20 14:41 UTC by Thomas Haller
Modified: 2020-11-14 05:56 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.20.0-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:30:06 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3623 0 None None None 2019-11-05 22:30:18 UTC

Description Thomas Haller 2019-08-20 14:41:03 UTC 
1.20.0 release enables support for FT (fast BSS transition).

It enables it (towards wpa-supplicant), if supplicant announces that it was built with support for it.


But some drivers don't do well with this, so we need to honor also the per-interface capabilities and avoid setting it.

Basically: backport upstream commit [1]. See commit message for further details.


[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/2f8a4e90f0fd0f900996e3081d49f8799bba4c6f
Comment 3 Thomas Haller 2019-08-20 14:49:34 UTC 
> Answer the following 3 questions:

> 1. What is the impact of waiting until the next release to include this BZ?   Reviewers want to know which RHEL features or customers are affected and if it will impact any Layered Product or Hardware partner plans.

If users happen to use a driver that does not support FT, and if their AP supports it, then they might end up unable to connect to the Wi-Fi network.

Possibly most drivers in stock RHEL support this. Though, I did not confirm whether that's the case 100%. Regardless, I think for a user it should still be possible to install an out-of-tree driver (on their own accord) and use it successfully. There are known non-upstream drivers that suffer from this problem.


> 2. What is the risk associated with the fix?  Reviewers want to know if the fix is contained, testable, and there is enough time to verify the work w> ithout impact the schedule or other commitments.

The fix is quite trivial. See the referenced patch.

Very worst case, the patch results in NM now *wrongly* detecting FT support as missing (despite being actually available). That would not be critical, it's just a Wi-Fi feature that then would be not used, while it could. Having said that, I tested the patch, and such a wrong detection seems purely hypothetical. It should work as intended...

> 3. Provide any other details that should be weighed in making a decision (Other releases affected, upstream status, business impacts, etc).

Fix is merged upstream.

This only affects upstream release 1.20.0 (which is packaged in rhel-8.1).
Comment 7 errata-xmlrpc 2019-11-05 22:30:06 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://access.redhat.com/errata/RHBA-2019:3623
Note You need to log in before you can comment on or make changes to this bug.