https://bugzilla.novell.com/show_bug.cgi?id=467980 Summary: wpa_supplicant blacklists wrong AP Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Major Priority: P5 - None Component: Mobile Devices AssignedTo: hschaa@novell.com ReportedBy: hschaa@novell.com QAContact: qa@suse.de CC: tambet@novell.com Found By: --- If wpa_supplicant gets new scan results and finds a better AP it tries to roam to that AP. Therefore it tells the driver to associate to the new AP. The driver will then disassociate from the previous AP and notify wpa_supplicant about that before it starts the association with the new AP. Unfortunately wpa_supplicant thinks that the association with the new AP failed and enters its internal state 'disconnected'. The new AP will get blacklisted and the supplicant starts a new scan to find a new AP. At a first glance this issue is not that bad as the supplicant will simply associate with another AP but the following problems attract attention: 1) The association will take much longer and thus the probability of NM timing out and taking the interface down is much higher. 2) The supplicant might select a worse AP (in regard to signal strength) because of blacklisting the better one. I'm not yet sure how to fix that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.