Date: Fri, 30 Sep 2005 21:07:16 -0500 From: Eric Schuele <e.schuele@computer.org> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: mobile@freebsd.org, current@freebsd.org Subject: Re: wpa_supplicant and WEP.... Message-ID: <433DEF54.7070201@computer.org> In-Reply-To: <20050930222442.GA20004@odin.ac.hmc.edu> References: <433D5215.6010101@computer.org> <20050930184537.GA3665@teardrop.org> <433DA1CF.7020502@computer.org> <20050930210541.GA11841@odin.ac.hmc.edu> <433DAE00.4090602@computer.org> <20050930222442.GA20004@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------090009070504080304070808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Brooks Davis wrote: > On Fri, Sep 30, 2005 at 04:28:32PM -0500, Eric Schuele wrote: > >>Brooks Davis wrote: >> >>>On Fri, Sep 30, 2005 at 03:36:31PM -0500, Eric Schuele wrote: >>> >>> >>>>James Snow wrote: >>>> >>>> >>>>>On Fri, Sep 30, 2005 at 09:56:21AM -0500, Eric Schuele wrote: >>>>> >>>>> >>>>> >>>>>>I have gotten wpa_supplicant to work fine for WPA-PSK and open sites... >>>>>>but I would like it to work with WEP as well. it appears to associate >>>>>>with a WEP site no matter what WEP key I give it. But whether the key >>>>>>is correct or not... I can not get a response from my DHCP server. >>>>>> >>>>>>My wpa_supplicant entry: >>>>> >>>>>... >>>>> >>>>> >>>>> >>>>>>wep_tx_keyidx=0 >>>>> >>>>> >>>>>I would try dropping this line. I use wpa_supplicant to connect to a >>>>>number of different wireless networks and for the WEP-only ones I've >>>>>never needed anything more than: >>>>> >>>>>ssid=... >>>>>key_mgmt=NONE >>>>>wep_key0=... >>>>> >>>> >>>>Still no go. The wep_key0 is the clear text passphrase, correct? Not >>>>one of the encrypted keys? right? >>> >>> >>>The entry in the example file shows both hex and ascii keys. No >>>excryption of keys is supported by standard WEP so if your AP is doing >>>something like that you need to get the hex key it's using from it. >> >>If I attempt to use the hex key... it fails to parse the wpa_supplicant >>file!?! The AP is a linksys something-or-other... and when you type in >>a cleartext passphrase it generates 4 hex keys. I have tried both the >>passphrase and the hex keys. > > > You definitly need to use the hex keys. Turning a password into four > hex keys is absolutly not part of the standard. Ah... hex *keys*... plural!! I should use all 4 of them? I had been using just the one declared as the default key to tx. I have attached a screenshot of what a linksys does when you setup WEP. Give it a cleartext passphrase and it generates 4 hex keys. On some systems you can enter the passphrase... others I've had to enter the 'default' key. Never thought to try all four keys at once. Is that what you think I should do? > How are you entering > your hex keys? The examples are a bit unclear, but digging around in > the code it looks like unquoted strings are assumed to be hex strings. > They should not be prefixed by 0x. I'll try them in the above format (I was prefixing with 0x). I'm not in the office but will try my home AP.... BRB.... Whoa!!! That's IT!!! Am I the only person who couldn't figure that out??? You must use all 4 hex keys and specify which is the default. Thank you very much! > The manpage needs some help in this > area. > > >>>Have you been able to connect by hand (not using wpa_supplicant)? If >>>not, do that first. >> >>Yes... I can connect using the following script > > > Good. Hopefully it's just a confusing config file issue. > > -- Brooks > -- Regards, Eric --------------090009070504080304070808--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?433DEF54.7070201>