https://bugzilla.novell.com/show_bug.cgi?id=389753
User hschaa@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389753#c18
--- Comment #18 from Helmut Schaa 2008-05-28 01:45:53 MDT ---
Daniel, I'm aware of the current KNM state.
But the change from NM 0.6.x to 0.7.x (although 0.7 is not even officially
released yet!) caused way more trouble then expected and we had to (and have
to) rework tons of code.
Nevertheless, after having a look at the NetworkManager log this issue only
happens for drivers which do not support wpa_supplicant's AP_SCAN=1.
NetworkManager uses AP_SCAN=2 which means the driver has to decide about the AP
selection and needs detailed instructions from the supplicant about the
WPA-capabilities to use.
Therefore it is ipw2100 which needs to get support for per-ssid-scans
(AP_SCAN=1) to make this feature work correctly. I'm not sure why that worked
in 10.3 as the driver never had that ability.
--
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.