Tag Info

wpa_supplicant does have support for ndiswrapper and should be run like this: wpa_supplicant -i wlan0 -D wext Instructions how to install ndiswrapper drivers - however I never use ndiswrapper. If it does not help you have to say what is the output of: wpa_supplicant -i wlan0 -D wext As a side note - to use WPA you need user program called wpa ...

Unfortunately I have to answer the question myself now. "Unfortunately" because the answer is "No, it is not possible". I took a look at how PAP is working, and came to the conclusion that it is logically impossible to store the password as a hash value. With PAP, the username and password are sent directly to the authentification side. Therefore, the ...

I have the same problem. /etc/network/interfaces Manpage says for dhcp method: hwaddress class address Hardware Address. class is one of ether, ax25, ARCnet or netrom. address is dependent on this choice. then maybe the problem is the class option. I'll try it. Other option is not supported by firmware.

I figured out the problem and thought I'd post it here in case someone else is having similar problems. The problem was that the network card was failing, but not fatally at first. About two weeks after the original question, the card completely failed, eventually becoming unresponsive but at the same time showing up in lsusb output. I pried open the ...

Do one of these: Instead of using hwaddress, try using pre-up ifconfig wlan0 hw ether 00:11:22:55:55:D1 This may not actually have been required, but I found that on my bonded interface, hwaddress did not work, the above ifconfig did. I would recommend you either create a bonded interface or a bridge (if bridge, you should be using bridge_hw ...

As last quote says, you have "dhcp", when you should have "manual" for wlan0. Try changing iface wlan0 inet dhcp to iface wlan0 inet manual in /etc/network/interfaces. Another choice is to use manager for network connections, for example Gnome's Network Manager or WICD.