linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pat Erley <pat-lkml@erley.org>
To: Larry Finger <Larry.Finger@lwfinger.net>,
	Erich Titl <erich.titl@think.ch>,
	linux-wireless@vger.kernel.org
Subject: Re: b43 driver and WEP
Date: Mon, 05 Jan 2015 17:49:27 -0600	[thread overview]
Message-ID: <54AB2307.7080409@erley.org> (raw)
In-Reply-To: <54AAFFB1.8030109@lwfinger.net>

On 01/05/2015 03:18 PM, Larry Finger wrote:
> On 01/05/2015 03:07 AM, Erich Titl wrote:
>> Hello
>>
>> I am working on a WLAN client on an embedded system and I am facing a
>> problem using WEP. I am using the b43 driver with a BCM43222 mini-pci
>> card and kernel 3.10.55.
>>
>> The card works fine with WPA and without encryption. Using WEP results
>> in a weird situation where dhcp requests can be sent across the wireless
>> link, but a dhcp reply is never received.
>>
>> The only error I could come up with is
>>
>> AP# ip link set wlan0 up
>> AP# iw event -f &
>> AP# iw wlan0 connect scoobly keys 0:abcdefghijklm
<<Snip>>
>>
>> [  417.886167] b43 ssb0:0 wlan0: failed to set key 0

Does the key have to be hexadecimal for iw, and is yours?  A lot of WEP 
APs will generate a hex key from a passphrase, but (from what I 
remember), linux requires the actual hex key.  This is just from hazy 
memory as the last time I used WEP without a gui controller (or even 
with) was years ago.


  reply	other threads:[~2015-01-05 23:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05  9:07 b43 driver and WEP Erich Titl
2015-01-05 21:18 ` Larry Finger
2015-01-05 23:49   ` Pat Erley [this message]
2015-01-05 23:53   ` b43 driver and WEP (solved) Erich Titl
2015-01-06  0:52     ` Larry Finger
2015-01-06  7:02       ` Erich Titl
2015-01-06  8:29       ` Johannes Berg
2015-01-06 10:38         ` Erich Titl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54AB2307.7080409@erley.org \
    --to=pat-lkml@erley.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=erich.titl@think.ch \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).