From: Michael Buesch <mb@bu3sch.de>
To: Paul Hampson <Paul.Hampson@pobox.com>
Cc: netdev@vger.kernel.org
Subject: Re: bcm43xx-d80211 broadcast reception with WPA
Date: Sat, 11 Nov 2006 16:07:05 +0100 [thread overview]
Message-ID: <200611111607.05420.mb@bu3sch.de> (raw)
In-Reply-To: <loom.20061111T070237-788@post.gmane.org>
Please _don't_ remove CCs.
On Saturday 11 November 2006 07:32, Paul Hampson wrote:
> Michael Buesch <mb <at> bu3sch.de> writes:
>
> > On Thursday 09 November 2006 23:23, Paul Hampson wrote:
> > > I've been backporting the bcm43xx-d80211 driver to whatever the released
> > > 2.6 kernel was using the rt2x00 project's d80211 stack (equivalent to
> > > current wireless-dev but with a workaround for not having a ieee80211_dev
> > > pointer and still using the _tfm interface instead of the _cypher interface.)
>
> > > As of last night's wireless-dev tree bcm43xx, everything seems to be
> > > operating fine except incoming broadcast traffic is coming in 14 bytes too
> > > long and scrambled. I presume this means it's not decrypting properly...
>
> > It sounds like a bug in the hardware decryption setup.
> > Are you using TKIP or not?
>
> Yes, it's using TKIP. The router docs and the loading of the tkip module
> when I use the softmac driver agree on this.
TKIP is still software encryption. Did you try with WPA-AES, for example,
which is hardware encryption?
The problem might be that the card tries to decrypt mcast
frames in the crypto hardware, although we did not set a key.
So it uses a random key to decrypt. That obviously results in crap.
--
Greetings Michael.
next prev parent reply other threads:[~2006-11-11 15:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 22:23 bcm43xx-d80211 broadcast reception with WPA Paul Hampson
2006-11-10 8:27 ` Ivo Van Doorn
2006-11-10 9:24 ` Paul Hampson
2006-11-10 20:12 ` Michael Buesch
2006-11-11 6:32 ` Paul Hampson
2006-11-11 15:07 ` Michael Buesch [this message]
2006-11-12 1:24 ` Paul TBBle Hampson
2006-11-12 8:34 ` Michael Buesch
2006-11-12 20:43 ` Ismail Donmez
2006-11-12 21:47 ` Michael Buesch
2006-11-12 22:40 ` Ismail Donmez
2006-11-12 22:41 ` Ismail Donmez
2006-11-12 22:54 ` Johannes Berg
2006-11-13 8:10 ` Ismail Donmez
2006-11-13 10:43 ` Jiri Benc
2006-11-14 14:29 ` Paul TBBle Hampson
2006-11-14 14:40 ` Johannes Berg
2006-11-14 15:53 ` Michael Buesch
2006-11-14 14:40 ` Paul TBBle Hampson
2006-11-14 14:41 ` Johannes Berg
2006-11-15 18:48 ` [PATCH, RFT]: Fix bcm43xx-d80211 hwcrypto (was Re: bcm43xx-d80211 broadcast reception with WPA) Michael Buesch
2006-11-16 12:34 ` [PATCH, RFT]: Fix bcm43xx-d80211 hwcrypto Paul TBBle Hampson
2006-11-16 14:07 ` [PATCH]: bcm43xx-d80211: fix hwcrypto issues (mcast) Michael Buesch
[not found] ` <200611161507.33971.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-11-17 7:46 ` Benjamin Herrenschmidt
2006-11-17 7:53 ` Johannes Berg
2006-11-17 8:02 ` Benjamin Herrenschmidt
2006-11-17 8:49 ` Paul Hampson
2006-11-17 10:35 ` Andreas Schwab
[not found] ` <jeveles6lx.fsf-+JVCjXrnBTholqkO4TVVkw@public.gmane.org>
2006-11-17 11:04 ` Johannes Berg
2006-11-17 11:30 ` Andreas Schwab
2006-11-17 22:59 ` Martin Langer
2006-11-17 13:20 ` Paul TBBle Hampson
2006-11-18 1:15 ` Paul TBBle Hampson
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=200611111607.05420.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Paul.Hampson@pobox.com \
--cc=netdev@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).