wpa_supplicant doesn't work with ndiswrapper anymore

[tim__b]

Binary package hint: wpasupplicant

Since upgrading to Ubuntu 7.04 Feisty Fawn wpa_supplicant stopped working with ndiswrapper. In my case I i used a BCM4318 Airforce One Chip with the same Win drivers I used in Edgy (in which it worked perfectly). Things are set up correctly, i find some networks and can connect to WEP one. Only WPA stopped working...
There are many users having the same problem (as reported in http://ubuntuforums.org/showthread.php?t=343383 ).

[Reinhard Tartler (siretart)]

that link doesn't work for me, it requires me to login. please copy relevant information to this bug.

Could you please try to attach debug logs? use -dd as wpa_supplicant parameters.

[tim__b (timb)]

Sorry, didn't know, that the forum needs an account to read. Attached is a ZIP containing:
file1.txt: $ sudo wpa_supplicant -i eth1 -dd -D wext -c/etc/wpa_supplicant/wpa_supplicant.conf
file2.txt: $ iwconfig
file3.txt: $ sudo dhclient eth1

WLAN is configured via ndiswrapper-utils-1.9. (Solution worked using Edgy, stopped working in Feisty).

[Hinne Hettema (hinneh)]

I had the same problem. In my case the machine seemed to authenticat but did not get an IP address. All worked in Dapper and Edgy. I since rebuilt on Dapper since this is my 'production' machine.

[JoeIntel (xyz00012)]

I've the same problem too. It worked fine under Dapper and Edgy, but since Feisty is wpa_supplicant not able to establish a connection. I use a AVM FRITZ!WLAN USB Stick under ndiswrapper.

[H.E. Pennypacker (klop2964)]

I can definitely add to this. I don't know if wpa_supplicant is having an issue with ndiswrapper, but I do know wpa_supplicant is have some issues at least. When issuing sudo /etc/init.d/networking restart, I would get the following problem (several lines from the entire output):

send_packet: Operation not permitted
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-post-down.d/wpasupplicant exited with return code 1
wpa_supplicant: cannot read contents of managed
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1
There is already a pid file /var/run/dhclient.eth1.pid with pid 134993416

I would then be told the hostname is invalid. Bizarre. I don't know what this all means. Either way, I am now using the Internet following a guide on Ubuntu forums, but I still can't connect to WPA2 using my BCM4318 card. One forum user reported having a working connection to a WPA2 access point using only AES, and not TKIP-AES (He has a BCM4318 card). Using only AES won't work for me.

[Reinhard Tartler (siretart)]

according to http://thread.gmane.org/gmane.linux.drivers.hostap/15839, it should help if you guys restrict usage of TKIP (wpa1 only). could you please read the linked thread retry again?

[tim__b (timb)]

I tried the TKIP Workaround, but still can't connect to my WPA1Personal Network.

[Reinhard Tartler (siretart)]

tim__b <email address hidden> writes:

> I tried the TKIP Workaround, but still can't connect to my WPA1Personal
> Network.

Please attach your debug log (run wpasupplicant with -dd, to compare
with the output on the hostap mailing list)

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

[tknieper (tobias-knieper)]

I'm having the same trouble since I upgraded this machine to edgy. I set the pairwise cipher to TKIP as described on the mailing list but pairing takes up to 100 attempts until success. I'll attach the wpa_cli log.

[Launchpad Janitor (janitor)]

[Expired for wpasupplicant (Ubuntu) because there has been no activity for 60 days.]