From: Dave <kilroyd@googlemail.com>
To: matthieu castet <castet.matthieu@free.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [Fwd: airo with WPA support merge]
Date: Sat, 05 Jul 2008 18:07:25 +0100 [thread overview]
Message-ID: <486FAA4D.2080601@gmail.com> (raw)
In-Reply-To: <486F46A7.4020105@free.fr>
matthieu castet wrote:
>> [2]
>> http://svn.gna.org/viewcvs/airo-wpa/branches/kernel-merge/
>>
>> [3]
>> Dan Williams :
>> One problem I have is that after setting the TKIP key, I always get a
>> sequence of 3 bad MICs, and then the MAC sends a status of 0x8117 which
>> causes the driver to send a disconnection event to userspace, which
>> makes wpa_supplicant fail the connection. If I comment out the 'goto
>> badrx;' in the interrupt handler where the WPA mic is checked,
>> everything works great and I can complete the 4-way handshake. It needs
>> more investigation, but do you have any thoughts on what might be going
>> on here?
I had a quick look at [2].
The WPA support is similar to that posted for the orinoco driver last weekend. The driver calculates the MIC using the current software keys and appends it to the packet to be transmitted; the firmware/hardware encrypts the packet with the keys set in hardware.
For orinoco the TKIP changing code waits until the card has finished transmitting queued packets before changing the keys [4]. This prevents the software keys from getting out of step with the hardware keys. Orinoco makes use of a RID to determine if there's anything in the TX queue, but I don't think this is necessary.
Might a similar change work for the airo driver?
Regards,
Dave.
[4] <http://marc.info/?l=linux-wireless&m=121467838917394&w=4>
prev parent reply other threads:[~2008-07-05 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4807C194.4040108@free.fr>
2008-07-05 10:02 ` [Fwd: airo with WPA support merge] matthieu castet
2008-07-05 17:07 ` Dave [this message]
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=486FAA4D.2080601@gmail.com \
--to=kilroyd@googlemail.com \
--cc=castet.matthieu@free.fr \
--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).