netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Paul TBBle Hampson <Paul.Hampson@Pobox.com>
Cc: netdev@vger.kernel.org, linville@tuxdriver.com,
	Michael Buesch <mb@bu3sch.de>
Subject: Re: bcm43xx-d80211 broadcast reception with WPA
Date: Tue, 14 Nov 2006 15:41:55 +0100	[thread overview]
Message-ID: <1163515315.2762.24.camel@ux156> (raw)
In-Reply-To: <20061114144040.GA18175@keitarou>

On Wed, 2006-11-15 at 01:40 +1100, Paul TBBle Hampson wrote:

> bcm43xx-d80211 w/v3 firmware and WEP-104: Garbled _everything_ RX
> Of course, that's to be expected. WEP only uses broadcast keys, and
> we knew they were failing in software mode.

Hmm, not sure about this, but it sort of confirms my theory -- with v3
firmware we never upload keys to the hw so the hw will successfully
decrypt frames with the 'none' algorithm, and the RX path will treat
them as though they were decrypted already.

johannes

  reply	other threads:[~2006-11-14 14:40 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
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 [this message]
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=1163515315.2762.24.camel@ux156 \
    --to=johannes@sipsolutions.net \
    --cc=Paul.Hampson@Pobox.com \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --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).