Re: [Madwifi-users] Re: WPA-PSK Fail (madwifi + hostapd)
Status: Beta
Brought to you by:
otaku
From: Vincent T. <vi...@bu...> - 2005-04-08 13:50:50
|
Hi again ! Well, it turns out in a way you were right ;-) I got it to work finally. It turns out my client machine is an IBM Laptop running Win XP SP2. Because it's an IBM Laptop, you get this tool called IBM Access Connection which lets you switch easily between different network profiles (wired, wireless, DSL, dialup, etc ...) It's actually quite handy ! I've been using this tool when running my tests (worked fine with WEP Open/shared auth, No WEP and all the rest) In this tool, when you setup WPA-PSK, you CAN use either 64 HEX digits of 8 to 63 text chars. neither worked. I then tried to use directly the Win XP wireless config panels where your only choice is to enter text chars, Well, believe it or not, in the minutre I was connected. I'm one happy user now :-) I'm actually writing this from the laptop over the WPA-PSK enabled WiFi link :-) Cheers ! Vince. Sebastian Weitzel wrote: >> Applied your patch to hostapd (no errors), compiled and ran. I get the >> same results :-( > > > I think your mistake is the wpa-psk key. You want a key which is max 63 > chars long and needs to be specified correctly. > > in hostapd.conf it has to be specified by: > > wpa_passphrase=qspI9sgsgbIkuipE3wZgnujC2lLM5MPJ2dGpPP40LWi7bk1aD6RRyWEpegLdUPV > > > while in wpa_supplicant.conf: > psk="qspI9sgsgbIkuipE3wZgnujC2lLM5MPJ2dGpPP40LWi7bk1aD6RRyWEpegLdUPV" > > You may also want to see my sample config at > http://rafb.net/paste/results/SyDmDx39.html > > |