Connecting to WPA wireless Network
Hi. I have a broadcom Linksys wireless G Adapter connecting to a WPA encoded wireless network.
Using Ndiswrapper, I have successfully gotten the driver installed, and it says the hardware and driver are both present. Now, what commands do I use to connect to a WPA wireless network? Or view the wireless networks in range of that card? thanks, LN75 |
/usr/local/bin/wpa_supplicant -Bw -c/etc/wpa_supplicant.conf -Dwext -iwlan0
iwlist wlan0 scan |
OK. The output of the first says that /usr/local/bin/wpa_supplicant doesn't exist(no such directory)
The output of the second says that the Interface doesn't support scanning. Does this mean I'm missing something? |
I guess that it is /usr/bin/wpa_supplicant (specify distro, by the way..)
About scanning - try 'iwlist wlan0 scan' after 'ip link set wlan0 up'. Try also 'iwlist scan'. Post lines in 'dmesg' output that appear after each command, beginning with loading ndiswrapper module. |
OK.
it Still says /usr/bin/wpa_supplicant isn't a file or directory. 'ip link set wlan0 up' gives Code:
SIOCGIFFLAGS: No Such device Code:
wlan0 Interface doesn't support scanning. Code:
lo Interface doesn't support scanning. |
"which wpa_supplicant" will give you the path, but the driver seems to be the issue.
Try lsmod |grep ndiswrapper to see if the module is loaded. If not, modprobe ndiswrapper. If it is, run ifconfig to see which interfaces are used. wlan0 is the default nomenclature, but your system may be different. |
OK
the path is: Code:
/sbin/wpa_supplicant But lsmod gave: Code:
ndiswrapper 194608 0 Modprobe gives back the command line, which I remember as good. this is what ifconfig gives back: Code:
eth0 Link encap:Ethernet HWaddr 00:12:3F:7E:B9:6C |
So I think
Code:
ip link set eth1 up |
Sorry, should have asked for iwconfig output as well. That will identify the expected wireless interface.
|
I forgot to mention that I'm using Ubuntu 7.
OK. doing '/sbin/wpa_supplicant -Bw -c/etc/wpa_supplicant.conf -Dwext -iwlan' just gives a command line back. So does 'ip link set eth1 up'. Is this supposed to happen? iwlist eth0 scan gives me: Code:
eth0 Interface doesn't support scanning. |
iwconfig gives:
Code:
lo no wireless extensions. |
Quote:
Clearly, eth1 is the wireless interface. (That's why you're getting the error when trying to scan for APs with eth0.) I'm guessing that the bcm43xx driver is loading and conflicting with ndiswrapper. Do you see bcm43xx in the output of lsmod? |
The output of lsmod is below:
Code:
Module Size Used by |
Yes. bm43xx is there in the list. What should I do to prevent it from interfering?
|
modprobe -r bcm43xx
That will unload the module. Edit your blacklist file to specify the bcm43xx as a module that should never load. On my machine, it's /etc/modprobe.d/blacklist Might be different on yours. |
All times are GMT -5. The time now is 11:23 AM. |