From: Saravana <saravanad@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: add debugfs file for mic failure
Date: Tue, 27 Nov 2012 11:27:50 +0530 [thread overview]
Message-ID: <50B4565E.6030105@posedge.com> (raw)
In-Reply-To: <1353942528.2800.1.camel@jlt4.sipsolutions.net>
On 11/26/2012 08:38 PM, Johannes Berg wrote:
> On Mon, 2012-11-26 at 04:56 -0800, saravanad@posedge.com wrote:
>> Add a debugfs file showing the number of failure of
>> rx packet dropped due to mic failures. currently the
>> number of rx packet dropped is counted in general and
>> not with respect to a specific reason. This patch
>> counts the number of packet drop due to mic failure.
>
> What's the value of this, shouldn't wpa_s/hostapd start countermeasures
> pretty quickly?
>
This will just be a counter which keeps track of the number of mic
failures. Debugfs already had Rx dropped packet counter. This would
provide more granularity in respect to the reason of packet drop.
Yes, wpa_s/hostapd will start countermeasure quickly.
> johannes
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-11-27 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 12:56 [RFC] mac80211: add debugfs file for mic failure saravanad
2012-11-26 15:08 ` Johannes Berg
2012-11-27 5:57 ` Saravana [this message]
2012-11-29 6:29 ` Saravana
-- strict thread matches above, loose matches on Subject: below --
2012-12-04 13:19 Saravana
2012-12-04 13:24 ` Johannes Berg
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=50B4565E.6030105@posedge.com \
--to=saravanad@posedge.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).