Red Hat Bugzilla – Bug 236528
TKIP errors when using WPA
Last modified: 2007-11-30 17:07:43 EST
Description of problem:
When attempting to use WPA with an Intel wireless card (ipw2200/ipw3945) on a
Dell D820 laptop once the wireless connection is put under load the connection
will eventually drop with errors similar to the following in the log:
TKIP: ICV error detected: STA=00:04:0e:7e:7a:58
N/A: Michael MIC verification failed for MSDU from 00:04:0e:7e:7a:58 keyidx=0
wlan: MSDU decryption/MIC verification failed (SA=00:04:0e:7e:7a:58 keyidx=0)
This is a known issue with the 1.1.13 version of the ieee80211 module
components, especially when running on SMP systems (very common with
hyperthreading and dual-core desktops everywhere). A patch has been available
for months, and versions of the ieee80211 stack >= 1.2.15 do not have this
Version-Release number of selected component (if applicable):
ieee80211 versions 1.1.13
Steps to Reproduce:
1. Configure any wireless card which uses the ieee80211 stack
2. Connect to a WPA enabled AP (WEP can cause the problem as well)
3. Pass a lot of traffic (usually hundreds of megabytes)
4. Watch the logs for errors such as "TKIP: ICV error detected" or "N/A: Michael
MIC verification failed for MSDU"
5. Connection will eventually drop and probably not recover easily.
Errors are logged and connection eventually drops
Wireless connection should be stable
I'll attache the patch that was posted on one of the ipw-devel lists for this
issue but it would probably be better to actually upgrade to a newer version of
the ieee80211 stack.
Created attachment 152663 [details]
Patch against ieee80211-1.1.14
The changes above have been committed to the RHEL5.1 kernel, which is now in beta.
Don, I found the changes in the following patch tracking file:
I have been running the RHEL5.1 beta kernel for several weeks on this same
laptop and the problem seems to be corrected. Thanks for the attention to this
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.