Wpa_supplicant is killing me

Caspian · 2008-01-10 18:35:15

Ok guys here's the thing; i've been trying to setup my homw wireless connection for two days now without success. I have D-link dwl-g650 pcmcia wireless card (atheros chipset so i use madwifi ofcourse) and Thomson SpeedTouch ST780 router. I've compiled ieee802.11 support in kernel (even it's not necessary as far as i know because i'm using madwifi). I'm trying to cennect to router using wpa-psk, but no luck. I'll give you all necessary config files and wpa_output, so PLEASE HELP ME BECAUSE I'M GOING MAD . Somethimes the router even asignes me ip address but i have no access to internet and both Act and Link lights blink on my card, so something went wrong....

/etc/wpa_supplicant/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=users
update_config=1

network={
ssid="SpeedTouch"
psk="D80163965E"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
}

And yes all the psk and ssid values are correct

Here's the wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf output:

Trying to associate with 00:90:d0:ea:06:c9 (SSID='SpeedTouch' freq=2412 MHz)
Associated with 00:90:d0:ea:06:c9
WPA: Key negotiation completed with 00:90:d0:ea:06:c9 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:90:d0:ea:06:c9 completed (auth) [id=0 id_str=]
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:90:d0:ea:06:c9 (SSID='SpeedTouch' freq=2412 MHz)
Associated with 00:90:d0:ea:06:c9
WPA: Key negotiation completed with 00:90:d0:ea:06:c9 [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:90:d0:ea:06:c9 completed (reauth) [id=0 id_str=]
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Trying to associate with 00:90:d0:ea:06:c9 (SSID='SpeedTouch' freq=2412 MHz)
Associated with 00:90:d0:ea:06:c9
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
WPA: Invalid EAPOL-Key MIC - dropping packet
ioctl[SIOCGIFADDR]: Cannot assign requested address
ioctl[SIOCGIFADDR]: Cannot assign requested address
ioctl[SIOCGIFADDR]: Cannot assign requested address
CTRL-EVENT-TERMINATING - signal 2 received --> this is work of my hands (Ctrl-c)

...........
And so on i think you get the point.
Then i tried wicd which would be perfect for me because i'm using fluxbox, but still nothing it would just say "can't connect". I even tried network-manager nad ohh the wonder it worked. But i really don't like netwotk mannager because of it's dependencies and so on.
Guys please help..........:(

.:B:. · 2008-01-10 18:39:09

Did you convert your passphrase? Wpa_supplicant does not use the 'plain' passphrase, you need to use wpa_passphrase to convert it to a hex string that wpa_supplicant will use then (it will even generate an excerpt for you that you can paste into your wpa_supplicant.conf).

Caspian · 2008-01-10 18:59:13

Well of course!!How stupid of me i forgot all about that. Thank you very much. Just one more question if i wish to use wicd now should i put the hex value given by wpa_passphrase in it as well?

SiC · 2008-01-10 19:46:47

Just append the output from wpa_passphrase to your wpa_supplicant.conf and then add the relevant other options. Should work.

Caspian · 2008-01-10 19:53:29

You didn't understand me. Wpa_supplicant works now, but i'm asking what psk key should i write in wicd the original or the wpa_passphrase one?? Because wicd doesn't work as well.

.:B:. · 2008-01-10 20:25:52

No, afaik the hex equivalent is only useful to wpa_supplicant itself (it is generated with the aid of the SSID).

Caspian · 2008-01-10 20:47:32

As i thought... So does anyone have an idea why wicd won't connect? wpa_supplicant and network-manager work but not wicd.

zyghom · 2008-01-10 21:59:49

Caspian wrote:

As i thought... So does anyone have an idea why wicd won't connect? wpa_supplicant and network-manager work but not wicd.

newest wicd is broken 1.4.1-2

Caspian · 2008-01-11 07:20:34

Ok, thanks. I'll try with the one from aur (1.3.6-1) and get back with results.

brain0 · 2008-01-11 07:56:23

B wrote:

Did you convert your passphrase? Wpa_supplicant does not use the 'plain' passphrase, you need to use wpa_passphrase to convert it to a hex string that wpa_supplicant will use then (it will even generate an excerpt for you that you can paste into your wpa_supplicant.conf).

That is not true. If you put the psk in " ", it is interpreted as ASCII and the hex value is automatically calculated. However, with many network blocks it may slow down wpa_supplicant, thus using wpa_passphrase could still be helpful.

Some more tips about wpa_supplicant:

- If you use WPA-PSK, you only have to set the ssid= and psk= options, the rest is chosen automatically. It is generally a good idea to set proto=RSN WPA though, because by default WPA is preferred, this setting ensures that WPA2 is preferred.
- There is a -Dmadwifi driver, no idea if it works better than -Dwext or works at all

Caspian · 2008-01-11 10:07:23

Thanks for your help brain0. madwifi driver works with wpa_supplicant as well. But wpa_supplicant isn't the problem anymore, it works now. I can't get wicd to work now and it would be very helpfull. Maybe i should start a new topic??

Arch Linux

#1 2008-01-10 18:35:15

Wpa_supplicant is killing me

#2 2008-01-10 18:39:09

Re: Wpa_supplicant is killing me

#3 2008-01-10 18:59:13

Re: Wpa_supplicant is killing me

#4 2008-01-10 19:46:47

Re: Wpa_supplicant is killing me

#5 2008-01-10 19:53:29

Re: Wpa_supplicant is killing me

#6 2008-01-10 20:25:52

Re: Wpa_supplicant is killing me

#7 2008-01-10 20:47:32

Re: Wpa_supplicant is killing me

#8 2008-01-10 21:59:49

Re: Wpa_supplicant is killing me

#9 2008-01-11 07:20:34

Re: Wpa_supplicant is killing me

#10 2008-01-11 07:56:23

Re: Wpa_supplicant is killing me

#11 2008-01-11 10:07:23

Re: Wpa_supplicant is killing me

Board footer