public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* TKIP: replay detected:  WTF?
@ 2006-02-17 23:40 Mark Lord
  2006-02-18  5:57 ` Jouni Malinen
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Lord @ 2006-02-17 23:40 UTC (permalink / raw)
  To: Linux Kernel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: TKIP: replay detected: WTF?
@ 2006-02-18  5:36 Larry Finger
  0 siblings, 0 replies; 3+ messages in thread
From: Larry Finger @ 2006-02-18  5:36 UTC (permalink / raw)
  To: linux-kernel

 > 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?

I have been getting similar messages; however, my previous TSC is almost always equal to the 
received TSC. I'm using the alpha bcm43xx driver with softmac, and thought it was a problem with the 
new code. Maybe not. Hmm.

Larry


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-02-18  5:59 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-17 23:40 TKIP: replay detected: WTF? Mark Lord
2006-02-18  5:57 ` Jouni Malinen
  -- strict thread matches above, loose matches on Subject: below --
2006-02-18  5:36 Larry Finger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox