From: Jouni Malinen <jkmaline@cc.hut.fi>
To: Jason Lunz <lunz@falooley.org>
Cc: linville@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: [PATCH] hush noisy ieee80211 CCMP printks
Date: Mon, 5 Jun 2006 06:31:48 -0700 [thread overview]
Message-ID: <20060605133147.GA9567@jm.kir.nu> (raw)
In-Reply-To: <20060605001208.GA4585@opus.vpn-dev.reflex>
On Sun, Jun 04, 2006 at 08:12:09PM -0400, Jason Lunz wrote:
> Don't swamp syslog with
> CCMP: decrypt failed: STA=00:12:17:3a:e2:c7
> and
> CCMP: replay detected: STA=00:12:17:3a:e2:c7 previous PN 000000000004 received PN 000000000004
> messages.
>
> These both seem to be completely normal in regular use, especially
> 'decrypt failed' whenever another wpa-using station on the same AP is
> within range.
These are not normal, i.e., they should not really show up unless
something goes wrong. In many cases, this may be caused by something
missing in local filtering (e.g., retry duplicates are not filtered out
correctly or messages to incorrect addresses are allowed through, etc.).
In other cases, it can indicate incorrect implementation of rekeying or
some other bugs in either end of the connection. Anyway, I don't have
anything against removing the messages in default kernel builds. If
there is a suitable build time debug option, that might be nicer way of
doing this, though, since these can provide valuable information when
figuring out why something does not work.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-06-05 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 0:12 [PATCH] hush noisy ieee80211 CCMP printks Jason Lunz
2006-06-05 13:31 ` Jouni Malinen [this message]
2006-06-05 16:03 ` Jason Lunz
2006-06-05 19:22 ` John W. Linville
2006-06-06 3:41 ` Jouni Malinen
2006-06-06 15:02 ` Jason Lunz
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=20060605133147.GA9567@jm.kir.nu \
--to=jkmaline@cc.hut.fi \
--cc=linville@tuxdriver.com \
--cc=lunz@falooley.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).