Date: Sat, 25 Aug 2001 20:10:11 -0700 From: Michelle Brownsworth <michelle@primelogic.com> To: Wesley Morgan <morganw@chemikals.org> Cc: freebsd-mobile@freebsd.org Subject: Re: WEP with Orinoco WaveLan Message-ID: <a0500193eb7ae1323c28b@[192.168.1.1]> In-Reply-To: <20010825210518.R37549-100000@volatile.chemikals.org> References: <20010825210518.R37549-100000@volatile.chemikals.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>I have two gold cards working fine with 128bit encryption, and have been >using them from 4.2-RELEASE to the current 4.x-STABLE. I would double and >triple check those keys, you may perceive them as being hex. Your >wicontrol output should indicate it as such: > >hex: >Encryption keys: [ 0xd41d8cd98f00bd41d8cd98f00b ] > >text: >Encryption keys: [ d41d8cd98f00b ][ ][ ][ ] > >It won't take 10 seconds to test the key as ascii... Wesley, You may be on to something there. Here's the wicontrol output: WEP encryption: [ On ] TX encryption key: [ 1 ] Encryption keys: [ ][ ][ ][ ] DOH! Key 1 is empty! What happened to the encryption key I entered using Orinoco's client manager on the Windows-based laptop? And why does the Windows machine work fine if there's no key present in Key 1? Oddly, I can't seem to find the correct incantation to obtain a key in ascii format, although man wicontrol states, "Using the additional -a flag will cause wicontrol to print out encryption keys as ascii characters instead of in hex." But the manpage also indicates that -a is access point density, so I'm confused. How do YOU get the key's ascii output? .\\ichelle >On Sat, 25 Aug 2001, Michelle Brownsworth wrote: > >> >On Sat, Aug 25, 2001 at 01:42:53PM -0700, Michelle Brownsworth wrote: >> >> I'm using an Orinoco Gold card in my laptop running 4.3-RELEASE. >> >> It was working fine without WEP, but when I changed it (and my >> >> SMC2655W) to 128-bit encryption it fails to make a connection. >> >> However, the same card works fine when I stick it in a Window >> >> laptop, so I know it's not a WEP key mismatch. I've seen some >> >> posts that seem to suggest that I should upgrade to 4.3-STABLE. >> >> Is it the consensus that upgrading will fix the WEP problem? >> > >> >I had a similar problem. It turned out that the setup program >> >which speaks via SNMP to the SMC2655W and the setup program for my >> >Hawking 802.11b card hashed the passphrase into entirely different >> >keys when working in 128 bit mode. >> > >> >I don't know it that's your problem, but check to see if your keys >> >are =really= the same. You might have to enter one end in hex to >> >match the other end. >> >> No, the keys were entered in hex, after thrashing with the string >> pass phrase problem you mention. Again, because it works perfectly >> in the Windows laptop I know there was no key mismatch. > >-- > _ __ ___ ____ ___ ___ ___ > Wesley N Morgan _ __ ___ | _ ) __| \ > morganw@chemikals.org _ __ | _ \._ \ |) | > FreeBSD: The Power To Serve _ |___/___/___/ > 6bone: 3ffe:1ce3:7::b4ff:fe53:c297 >Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a0500193eb7ae1323c28b>