WPA wifi. Help please! (I am desperate)

David david.maillists
Thu Jul 26 18:45:04 PDT 2007

Thank you very much.

Uf, still desperate. I tried to write the wpa_supplicant.conf, run
wpa_supplicant and then dhclient. The output of wpa_supplicant did not make
me be optimistic and, of course, dhclient failed.

What do I have to do? Is this sequence right?

1) Write the wpa_supplicant.conf file.
2) Run wpa_supplicant -dd -D madwifi -i ath0 -c /etc/wpa_supplicant.conf and
leave it running?
3) Then, dhclient ath0?

If not, can you please correct me?

If yes, can you please tell me the wpa_supplicant.conf file, based on the
output of iwlist ath0 scan that I wrote in the previous email? (sorry if I
look to be abusing, but I have tried for 5 hours with no results :-(  ).

Thank you very much for your help,


On 27/07/07, Bryan Kadzban <bryan at kadzban.is-a-geek.net> wrote:
> Hash: RIPEMD160
> David wrote:
> > They told me that it is right, but that WPA keys can be shorter than
> > 64 characters as well...
> *Only* if the string is treated as an ASCII key (the type of key that
> gets hashed with the SSID to generate the real key).  There is no way to
> treat a 26-character string as a hex WPA key; WPA keys are 256 bits
> long.
> > Maybe a hint can come from the fact that, in Windows XP, introducing
> > the 26 character key works OK.
> I have no idea how XP's supplicant is coded, but I suspect that it
> treats any string shorter than 64 characters as an ASCII key and hashes
> it.  For wpa_supplicant, try putting the key in double quotes, since
> that's what flags wpa_supplicant to treat the string as an ASCII key and
> hash it.
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> iD8DBQFGqSkbS5vET1Wea5wRA5eCAKCf4CWm2jD5gYOmVHBIwunqmzCgzwCfVkdf
> =7NBe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20070727/80373654/attachment.htm 

More information about the Hostap mailing list