WPA wifi. Help please! (I am desperate)

[Smith, Bruce]

There are quite a few examples on how to do wpa_supplicant configuration - just google it.  Yes, you leave it running.  If you do iwconfig <interface> it will tell you the status.  
 
You also have to set what WPA; is it 1 or 2.  1 is TKIP, 2 is AES.  For AES you set:
network {
proto=WPA2
key_mgmt=WPA-PSK
psk="blah"
auth_alg=OPEN
}
 
in the config file.
 
If you put psk in quotes, it is treated as a ascii passphrase, otherwise I believe its hex.
 
Shouldn't this be posted on a wpa_supplicant list?
 
Cheers,
Bruce
 
 

________________________________

From: hostap-bounces+bsmith=road-inc.com at shmoo.com on behalf of David
Sent: Thu 7/26/2007 6:45 PM
To: Bryan Kadzban
Cc: hostap at shmoo.com
Subject: Re: WPA wifi. Help please! (I am desperate)


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,

David



On 27/07/07, Bryan Kadzban <bryan at kadzban.is-a-geek.net > wrote: 

	-----BEGIN PGP SIGNED MESSAGE-----
	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.
	-----BEGIN PGP SIGNATURE-----
	Version: GnuPG v1.4.7 (GNU/Linux)
	Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
	
	iD8DBQFGqSkbS5vET1Wea5wRA5eCAKCf4CWm2jD5gYOmVHBIwunqmzCgzwCfVkdf 
	UYDRlQHPWzY/0cBA3LKpecE=
	=7NBe
	-----END PGP SIGNATURE-----
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20070726/7ca2f1a0/attachment.htm