From: Mark Lord <lkml@rtr.ca>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: TKIP: replay detected: WTF?
Date: Fri, 17 Feb 2006 18:40:51 -0500 [thread overview]
Message-ID: <43F65F03.1080001@rtr.ca> (raw)
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
Feb 17 18:38:48 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000002
Feb 17 18:38:48 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000003
Feb 17 18:38:48 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000004
Feb 17 18:38:48 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000005
Feb 17 18:38:48 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000006
Feb 17 18:38:48 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000007
Feb 17 18:38:48 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000008
Feb 17 18:38:48 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000009
Feb 17 18:38:48 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 00000000000a
Feb 17 18:38:54 localhost kernel: printk: 1 messages suppressed.
Feb 17 18:38:54 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 00000000000c
Feb 17 18:38:58 localhost kernel: printk: 2 messages suppressed.
Feb 17 18:38:58 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 00000000000f
Feb 17 18:39:07 localhost kernel: printk: 2 messages suppressed.
Feb 17 18:39:07 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000012
Feb 17 18:39:08 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000013
Feb 17 18:39:25 localhost kernel: printk: 1 messages suppressed.
Feb 17 18:39:25 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000015
Feb 17 18:39:26 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000016
Feb 17 18:39:27 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000017
Feb 17 18:39:35 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000018
Feb 17 18:39:36 localhost kernel: TKIP: replay detected: STA=00:13:46:16:96:b8 previous TSC ffff80723500 received TSC 000000000019
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.
Either this is "normal" behaviour, in which case the code should NOT be spamming me,
or something is broken, in which case.. what?
Cheers
next reply other threads:[~2006-02-17 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 23:40 Mark Lord [this message]
2006-02-18 5:57 ` TKIP: replay detected: WTF? Jouni Malinen
-- strict thread matches above, loose matches on Subject: below --
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=43F65F03.1080001@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-kernel@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