[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Using WPA without wpa_supplicant?



On Sat, 2005-10-22 at 18:33 +0200, François TOURDE wrote:
> 
> I think you will win on this challenge :)
> 
> I've tried some WPA-PSK configs with wpa_supplicant, and all what I
> can have is:
> 
> Oct 22 17:30:49 mersenne kernel: ipw2200: Firmware error detected.  Restarting.
> Oct 22 17:31:20 mersenne last message repeated 10 times
> Oct 22 17:32:23 mersenne last message repeated 21 times
> Oct 22 17:33:24 mersenne last message repeated 20 times
> Oct 22 17:34:24 mersenne last message repeated 20 times
> Oct 22 17:34:25 mersenne dhclient: receive_packet failed on eth1: Network is down
> 
> I've the 1.0.4-1 firmware for my ipw2200 card, so I will try (later)
> the new one.
> 
> I'm interested by your scripts using wpa_supplicant, it can be very
> usefull when I will upgrade to 1.0.6 ipw2200 driver.

I guess the first thing would be to try using the testsupplicant script
in whereami >0.3.23 or so.

wpa_supplicant is (along with every other thing :-) trying to manage all
networks, so the testsupplicant script:
 - sets the card to encrypted, key ff-ffff-ffff, open.
 - brings the interface up.
 - starts wpa_supplicant (or reloads it if it is currently running).
 - keeps looking to see if encryption is enabled within 15 seconds
 - either succeeds of gives up.

Some things I don't know and would like to work out with this script:
 - Should it use wpa_cli to figure if wpa_supplicant succeeds?
 - Should it stop wpa_supplicant if it fails?
 - Is 15 seconds long enough?

Regards,
					Andrew McMillan.

-------------------------------------------------------------------------
Andrew @ Catalyst .Net .NZ  Ltd,  PO Box 11-053, Manners St,  Wellington
WEB: http://catalyst.net.nz/            PHYS: Level 2, 150-154 Willis St
DDI: +64(4)803-2201      MOB: +64(272)DEBIAN      OFFICE: +64(4)499-2267
                  "Elvis is my copilot."
-- Cal Keegan
-------------------------------------------------------------------------

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: