Red Hat Bugzilla – Bug 249322
wpa_supplicant fails to/incorrectly re-associates after S3 suspend
Last modified: 2008-08-02 19:40:35 EDT
Description of problem:
I'm running a laptop with WiFi and wpa_supplicant, connecting to a AP with WPA
encryption. After resuming from suspend, the wireless adapter connects to the
first available (unencrypted) access point and ignores the AP it was using
before it suspended. In particular, the new AP that it connects to is not
listed in the wpa_supplicant.conf, and would not have been a valid connection at
Version-Release number of selected component (if applicable):
Most of the time.
Steps to Reproduce:
1. associate with an AP using WPA via wpa_supplicant
2. suspend, then resume
3. note the new AP that the machine connects to. If there's an unencrypted AP
close enough, the WiFi adapter will associate with it first.
The wireless adapter should only associate with the AP's listed in
I should also point out that this is a security issue. The Wifi adapter should
not be associating with foreign APs unless the user specifically authorizes it.
I'm not sure whose unencrypted "linksys" AP I was connecting to when the laptop
resumed, but I'm sure neither of would approve...
One workaround is to take the interface down before the computer is suspended;
this is kind of a hack and I've also noticed that it doesn't always work --
wpa_supplicant will sometimes still connect to the foreign AP.
Fedora Core 8
Associate with a configured SSID. If the connection fails,
NetworkManager associates with a "randon" open AP. Documentation
states that NM will only associate if the AP has been selected.
Since the list of AP's gets updated, it is not hard to accidentally
select the wrong one by mistake, so there needs to be a way to
clear the list of AP's to be used, and/or an option to use only
those in wpa_supplicant.conf.
"I should also point out that this is a security issue. The Wifi adapter should
not be associating with foreign APs unless the user specifically authorizes it."
This ^^^ is a kernel driver issue, and not something easy to control. Many
cards firmware will actively attempt to associate with an AP until it's told to
associate with some other AP explicitly. This behavior is not related to, or
under the control of, wpa_supplicant in any way. Some drivers have module
options (iwlwifi and ipw do) to disable this behavior.
@george: can you be more specific? NM itself will _never_ tell wpa_supplicant
to associate with an AP that you haven't chosen yourself at some point from the
menu. The card and driver may associate with random APs due to firmware or
driver decisions, which could be a security issue, although if the device does
not have an IP address the risk is mitigated.
What do you mean when you say "clear the list of APs to be used?" You mean
clear the list of APs that NetworkManager will allow the machine to associate
with? This bug is also about wpa_supplicant, so if you have a specific
NetworkManager bug, please file a separate bug targetted at the NetworkManager
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.