Description of problem: While running wpa_supplicant manually connecting to OPEN/WEP/WPA networks is possible, wheras running it as service is not. Investigation shows, that /etc/sysconfig/wpa_supplicant DRIVERS="-Dndiswrapper" instead of DRIVERS="-Dwext". This variable is used in the /etc/init.d/wpa_supplicant script when starting the service. Version-Release number of selected component (if applicable): wpa_supplicant 0.5.7-3 How reproducible: cat /etc/sysconfig/wpa_supplicant Actual results: DRIVERS="-Dndiswrapper" Expected results: DRIVERS="-Dwext"
I'm not really sure this is a bug per-se, because you obviously need to change the config file for wpa_supplicant to match your local hardware configuration. It may work by default with more peoples setups with "-Dwext", but you still need to change INTERFACES to whatever your interface is, regardless of what DRIVER is... So basically, ndiswrapper should get changed to wext yes, but your expected result is wrong because you have to configure it manually anyway.
OK, but it shouldn't be set to ndiswrapper in the first place, as it seems to be not part of the repository. There is some other shortcoming, which would make it easier to find out what's going on: in /etc/init.d/wpa_supplicant start() { echo $"Starting $prog: $conf, $interfaces, $drivers" should read start() { echo $"Starting $prog: $conf, $INTERFACES, $DRIVERS" so you are aware which driver is actually being referenced. Also using ndiswrapper without it being installed leads to really nasty problems in my installation ( FSC Amilo Si1520 Notebook with ipw3945 WLAN ).
*** Bug 248444 has been marked as a duplicate of this bug. ***
wpa_supplicant-0.5.7-4.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update wpa_supplicant'
wpa_supplicant-0.5.7-4.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.