Bug 2132255
| Summary: | RFE: add possibility to keep pairwise master key (PMK) around when disconnecting from network and use it for roaming when same SSID is available again | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | David Jaša <djasa> |
| Component: | wpa_supplicant | Assignee: | Davide Caratti <dcaratti> |
| Status: | CLOSED MIGRATED | QA Contact: | Laura Trivelloni <ltrivell> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.1 | CC: | rvr, sukulkar |
| Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-21 10:54:37 UTC | Type: | Story |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2132258 | ||
NM part reported as the bug 2132258. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Created attachment 1916140 [details] example NM & wpa_supplicant log with eager PMK removal during suspend Description of problem: Currently, it's impossible to resume connection to OTP wifi after suspend so practically, when user is connected to OTP wifi and needs to e.g. move between meeting rooms, they have to enter OTP again and they have all the TCP connections using this wifi (think IRC and SSH) severed despite reconnecting within TCP timeout. So in offices with Linux-powered laptops and OTP wifi, you can see lots of folks carrying open laptops around. For OpenVPN, analogous situation is handled by what NM exposes as vpn.persistent setting. When true, OpenVPN session keys are kept around even when underlying connection goes down, meaning that OpenVPN connection resumes after (reasonably short) suspend or even when underlying connection is replaced by different one (e.g. alternating between wired, regular wifi and connectivity shared by cell phone). It should be possible to have this feature in wpa_supplicant as well if wpa_supplicant: * had some means to set that PMK secrets are to be kept around even when disassociated from AP from any other reason than explicit user (or controlling sw) request * would try to roam to SSID for which it has PMK available Open question is whether there should be some sort of timeout after which PMK is discarded anyway or if this should be left entirely on AP side (and if it should be configurable). NM exposes no such settings for vpn.persistent connections. Version-Release number of selected component (if applicable): wpa_supplicant-2.10-4 How reproducible: always