Am Sonntag 24 September 2006 12:32 schrieb Christian:
> And I get loads of the "TKIP: replay detected..." messages as well.
Well, just remove those crappy messages (see attachment). Those messages are
not even worth the cpu cycles that they cause.
That you can receive the same package multiple times in a _very_ short time is
abolutely no surprise on a wireless link.
This patch made my dmesg at least usable again.
HS
Index: linux-2.6.17/net/ieee80211/ieee80211_crypt_ccmp.c
===================================================================
--- linux-2.6.17.orig/net/ieee80211/ieee80211_crypt_ccmp.c 2006-09-10 13:34:36.809747250 +0200
+++ linux-2.6.17/net/ieee80211/ieee80211_crypt_ccmp.c 2006-09-10 13:34:52.062700500 +0200
@@ -326,6 +326,7 @@
pos += 8;
if (memcmp(pn, key->rx_pn, CCMP_PN_LEN) <= 0) {
+#if 0
if (net_ratelimit()) {
printk(KERN_DEBUG "CCMP: replay detected: STA=" MAC_FMT
" previous PN %02x%02x%02x%02x%02x%02x "
@@ -333,6 +334,7 @@
MAC_ARG(hdr->addr2), MAC_ARG(key->rx_pn),
MAC_ARG(pn));
}
+#endif
key->dot11RSNAStatsCCMPReplays++;
return -4;
}
Index: linux-2.6.17/net/ieee80211/ieee80211_crypt_tkip.c
===================================================================
--- linux-2.6.17.orig/net/ieee80211/ieee80211_crypt_tkip.c 2006-09-10 13:33:47.410660000 +0200
+++ linux-2.6.17/net/ieee80211/ieee80211_crypt_tkip.c 2006-09-10 23:42:05.661101500 +0200
@@ -417,12 +417,14 @@
if (iv32 < tkey->rx_iv32 ||
(iv32 == tkey->rx_iv32 && iv16 <= tkey->rx_iv16)) {
+#if 0
if (net_ratelimit()) {
printk(KERN_DEBUG "TKIP: replay detected: STA=" MAC_FMT
" previous TSC %08x%04x received TSC "
"%08x%04x\n", MAC_ARG(hdr->addr2),
tkey->rx_iv32, tkey->rx_iv16, iv32, iv16);
}
+#endif
tkey->dot11RSNAStatsTKIPReplays++;
return -4;
}
@@ -452,10 +454,12 @@
* it needs to be recalculated for the next packet. */
tkey->rx_phase1_done = 0;
}
+#if 0
if (net_ratelimit()) {
printk(KERN_DEBUG "TKIP: ICV error detected: STA="
MAC_FMT "\n", MAC_ARG(hdr->addr2));
}
+#endif
tkey->dot11RSNAStatsTKIPICVErrors++;
return -5;
}
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
