Ivan Glushkov wrote:
Exactly that was the problem. Thank you. But now I get: #wpa_supplicant -i eth1 -D ipw ioctl[SIOCSIWPMKSA]: Operation not supported CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys Trying to associate with xx:xx:xx:xx:xx:xx (SSID='MyNet' freq=0 MHz) Associated with xx:xx:xx:xx:xx:xx ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Invalid argument Failed to set encryption. WPA: Failed to set PTK to the driver. Authentication with xx:xx:xx:xx:xx:xx timed out. Trying to associate with xx:xx:xx:xx:xx:xx (SSID='MyNet' freq=0 MHz) Associated with xx:xx:xx:xx:xx:xx ioctl[IPW_IOCTL_WPA_SUPPLICANT]: Invalid argument Failed to set encryption. WPA: Failed to set PTK to the driver. CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Be sure to check out the ipw2200 bugtracker at: http://www.bughost.org/bugzilla/I ran into a problem like this recently, and was able to get around it by adding a "hwcrypto=0" option to the ipw2200 driver. (For 2.6.x kernels, I think you do this by creating a file {the name isn't important, but you might as well call it "ipw2200"} in /etc/modprobe.d with the contents:
options ipw2200 hwcrypto=0This, apparently, turns off the hardware-based encryption in the ipw2200.... which isn't much of a problem because wpa_supplicant can do it in software. HOWEVER.... wpa_supplicant doesn't seem to do WEP. So, if you use hwcrypto=0, you'll probably lose the ability to connect to any WEP-only AP's (I did, anyway).
- Joe