Can't figure out wpa-supplicant problem
Some reason I just can't get wpa-supplicant to work.
I have my wireless network working. I can connect to unsecured and WEP (without wpa-supplicant) secured routers, but not WPA secured routers yet. I have the bcm43xx drivers in ndiswrapper. My router is secured: Security Mode: WPA Personal WPA Algorithim: AES WPA Shared Key: XXXXXXX # ndiswrapper -l Code:
Debsidian:/home/replica# ndiswrapper -l Code:
eth0 Scan completed : Code:
ctrl_interface=/var/run/wpa_supplicant Code:
Initializing interface 'eth0' conf '/etc/wpa_supplicant.conf' driver 'ndiswrapper' ctrl_interface 'N/A' bridge 'N/A' Code:
Initializing interface 'eth0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A' |
Your post seems to have a couple of contradictions. Clarify a few things, please.
You say you loaded the bcm43xx drivers in ndiswrapper. If you mean you loaded the Windows drivers using ndiswrapper, OK. Otherwise, you may have a driver conflict. Use bcm43xx or ndiswrapper, but not both. The fact that your interface is showing as eth0 vs. wlan0 points to the fact the bcm43xx is loading. Also, only call the driver in the wpa_supplicant using Dwext. Is the ESSID broadcast turned off? If so, try enabling it. |
Well I have wpa_supplicant working now, not really sure what I did to finally get it working. I even have it so it's connected on boot (/etc/network/interfaces)
My wireless was already working before, it just wasn't connecting to the router when WPA was enabled. Before I could connect with no security or WEP secured. |
I've found, as you did, that the -Dndiswrapper setting fails to work.
I've also found that the values in /etc/sysconfig/wpa_supplicant need to be changed too, since (on a Fedora system, at least) /etc/init.d/ndiswrapper runs that script to get its option settings. And (again, on a Fedora system), the NetworkManager uses the init.d script to start wpa_supplicant when it's needed. Oh, the newer b43 driver seems to work a little better than the bcm43xx one. And, as 2Gnu said, if you're using the b43 or bcm43xx driver, you should not be using ndiswrapper at all. (You do need to extract the microcode from the Windows .sys file -- use fwcuttewr-bcm34xx to do this -- before the FOSS drivers will work. |
without ndiswrapper my wireless doesn't work. I'm using the bcmwl5 drivers in ndiswrapper.
if I don't "#modprobe ndiswrapper" I don't get a wlan0 or eth0 Code:
Debsidian:/home/replica# ifconfig |
Yes, sorry: I read "bcmwl5" as "bcm43xx" since I just went through dropping ndiswrapper for b43, and my mind overrode my sight. But your setup is one I used for years (until it broke after Fedora added the b43 driver to their kernel), so, if it works for you on your distribution, that's great.
|
Well so far I've had no issues with ndiswrapper. My friend has an identical laptop running WinXP and I can get a better connection than him. I'll keep an eye out for that b43 though.
|
All times are GMT -5. The time now is 11:00 AM. |