Red Hat Bugzilla – Bug 243510
wlassistant can't connect to wpa encrypted network
Last modified: 2008-04-01 11:15:03 EDT
Description of problem: wlassistant can't connect to wpa encrypted network Version-Release number of selected component (if applicable): How reproducible: Every Time. Steps to Reproduce: 1. Open wlassistant 2. Connect to wpa encrypted network 3. Actual results: Failed appears, Terminal says: ACTION: CONNECT. Running DHCP client found. kill_dhcp: /sbin/dhclient -r ath0 No pre-connection command specified. iwconfig_set: /sbin/iwconfig ath0 mode managed channel 11 key off essid Nywag iwconfig_ap: /sbin/iwconfig ath0 ap 00:04:0E:7A:29:E5 ==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory Using wpa_supplicant driver: wext WPA client started. Waiting for status... ==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory CONNECTION FAILED. Expected results: Should connect ;) Additional info:
Have you already tried to install NetworkManager and use it (knetworkmanager is the KDE front-end) instead? Support for Intel 3945, rt2x00 and zd1211 based devices among others. It also supports: * Wired Ethernet Devices (IEEE 802.3) * Wireless Ethernet Devices (IEEE 802.11): Unencrypted, WEP, WPA Personal, WPA Enterprise * Virtual Private Network (VPN): OpenVPN, VPNC * Dial-Up (PPP) According to the F7 official FAQ: "the plan for Fedora 8 is to more deeply integrate Network Manager throughout the distribution and enable it by default in all instances".
Thanks, I use NetworkManager already. But I wanted to connect with wlassistant and that sadly did not work to a WPA protected network.
Are you using madwifi? I don't think that wlassistant knows how to handle passing the right driver to wpa_supplicant in the madwifi case.
I am running into the same problem w/ wlassistant. Both wlassistant and Network manager can detect the networks but neither can connect to them. NewtorkManager will spin for a while upon network selection, then will prompt me to enter the password (WPA/TKIP/Preshared) (which is already located in the keyring), then just stop (no connection). wlassistant gives the exact same output as that of the original poster. Wireless worked flawlessly on Fedora 7 as described in my blog post here (http://mohammed.morsi.org/blog/?q=node/218). Full diagnosis and relevant command output can be found in my FedoraForumn inquiry here (http://forums.fedoraforum.org/showpost.php?p=941955&postcount=9)
Mohammed, I can successfully connect to my WPA + WPA2 network using my broadcom chip + NetworkManager but I did not try wlassistant again. I have the following ideas: Can you check if you have the latest f8 updates? You could also try to remove the Broadcom Firmware in /lib/firmware and re-extract it.
Ah and by the way, try not to use ndiswrapper but use the bcm43 driver completly, instead: Remove ndiswrapper, kmod-ndiswrapper and the line you added to /etc/rc.local. After, eventually re-extract the firmware and reboot. The bcm43 linux driver really works *very* well (as well as the madwifi driver) in F8. If you still have to use that ndiswrapper trick, you should maybe report a bug against Fedora saying that your WLAN chip does not work properly. Also attach dmesg output.
Martin, can you reproduce this with the bcm43 driver (not madwifi)? I don't have ready access to a WPA enabled network.
I'm closing this out, feel free to reopen if you can reproduce this with bcm43.