From: Jouni Malinen <jkmaline@cc.hut.fi>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: TKIP: replay detected: WTF?
Date: Fri, 17 Feb 2006 21:57:36 -0800 [thread overview]
Message-ID: <20060218055736.GE8579@jm.kir.nu> (raw)
In-Reply-To: <43F65F03.1080001@rtr.ca>
On Fri, Feb 17, 2006 at 06:40:51PM -0500, Mark Lord wrote:
> Lately I've been seeing my kernel logs spammed by these events:
>
> Feb 17 18:38:48 localhost kernel: TKIP: replay detected:
> STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000001
netdev could be better mailing list for this kind of issue. Anyway, it
looks like something managed to set the last packet number to very high
number which will make all future frames dropped as replays.
> This is with the various 2.6.16-rc*-git* kernels, and possibly older 2.6.15
> series as well.
> They always seem to arrive in large bursts, like the bunch shown above.
> Using wifi
> over ipw2200 to a WPA2 AP.
Are you using wpa_supplicant to take care of the WPA2 handshake? If yes,
it would be interesting to see debug log from it for the key handshake
that happened just prior to this replay issue occurring.
> Either this is "normal" behaviour, in which case the code should NOT be
> spamming me,
> or something is broken, in which case.. what?
This is not normal behavior, i.e., something is indeed broken
(driver/supplicant/AP). Though, the those messages could be disabled by
default if there were a useful counter for detecting this kind of issues
easily. Anyway, these debug messages are quite useful in figuring out
what could have caused the "replays".
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-02-18 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 23:40 Mark Lord
2006-02-18 5:57 ` Jouni Malinen [this message]
2006-02-18 5:36 Larry Finger
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=20060218055736.GE8579@jm.kir.nu \
--to=jkmaline@cc.hut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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
all inboxes | Powered by JetHome®