From: Larry Finger <larry.finger@lwfinger.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH V3] mac80211: Turn off meaningless TKIP message when software WEP encryption is used
Date: Mon, 13 Aug 2007 18:13:49 -0500 [thread overview]
Message-ID: <46C0E5AD.2080407@lwfinger.net> (raw)
In-Reply-To: <200708140054.22845.IvDoorn@gmail.com>
Ivo van Doorn wrote:
>
> Not a question regarding the patch itself, but more about the comment
> regarding IEEE80211_HW_WEP_INCLUDE_IV and WEP encryption. ;)
>
> You mean the drivers that require mac80211 to do the encryption/decryption
> must make sure the IEEE80211_HW_WEP_INCLUDE_IV is _not_ set?
> I figured that when device requires software encryption they should set the flag
> since they do not touch the frame and pass it through completely to the stack
> this would also mean that the IV is passed on. Which should suggest that the
> flag should be set to tell mac80211 it can use the IV.
I'm not too up on this myself, but when I ported the frond end of bcm43xx-mac80211 to b43legacy, I
left the flags supplied to mac80211 untouched. Once I got the basic engine running using V3, rather
than V4, firmware, it did WPA encryption just fine. Of course, WPA is done in software in both
instances. WEP encrypt/decrypt is done in hardware in bcm43xx-mac80211, but it does not work in V3.
The only way I could get software-based WEP to work was to get rid of the "set_key" callback, which
sets an internal flag called force_sw_encrypt, and kill that flag. Then both WEP and WPA worked in
software, but the message showed up for WPA.
Yes, this empirical behavior does not seem to match one's intuition on what the flag should do.
Of course my patch is a complete hack that is band-aiding over a deeper flaw/bug in mac80211;
however, my request for a fix has gone unanswered. In addition, this problem is preventing me from
sending b43legacy to John. I originally intended to use my hack only while debugging, but when no
fix was coming, I decided that an awful patch would probably get some action. We'll see,
particularly now that my deep/dark secret is exposed. ;-)
Larry
next prev parent reply other threads:[~2007-08-13 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 22:13 [PATCH V3] mac80211: Turn off meaningless TKIP message when software WEP encryption is used Larry Finger
2007-08-13 22:54 ` Ivo van Doorn
2007-08-13 23:13 ` Larry Finger [this message]
2007-08-13 23:58 ` Michael Wu
2007-08-14 0:24 ` Larry Finger
2007-08-20 17:55 ` Ivo van Doorn
2007-08-21 10:17 ` Johannes Berg
2007-08-15 0:16 ` Johannes Berg
2007-08-15 13:16 ` Larry Finger
2007-08-15 13:30 ` Johannes Berg
2007-08-16 22:32 ` Johannes Berg
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=46C0E5AD.2080407@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).