From: drago01 <drago01@gmail.com>
To: Jouni Malinen <j@w1.fi>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
Dan Williams <dcbw@redhat.com>,
ipw3945-devel <ipw3945-devel@lists.sourceforge.net>,
Zhu Yi <yi.zhu@intel.com>
Subject: Re: mac80211 / iwl3945 + dynamic wep (again)
Date: Wed, 28 Nov 2007 15:06:17 +0100 [thread overview]
Message-ID: <474D75D9.7070908@gmail.com> (raw)
In-Reply-To: <20071127033408.GB5698@jm.kir.nu>
Jouni Malinen wrote:
> On Mon, Nov 26, 2007 at 03:50:00PM +0100, dragoran wrote:
>
>> btw would it make sense to ratelimit
>>
>> "WEP decrypt failed (ICV)" messages?
>> they are a bit annoying when connected to this network...
>>
>> dmesg | grep ICV | wc -l
>> 3489
>>
>> after some minutes.
>>
>
> While I fully agree that these messages should be rate limited, it is
> somewhat surprising to see this large a number of reported ICV failures.
> Does the ipw3945 not filter out FCS errors before passing the frame for
> WEP decryption? Or is there something odd about this network/client
> configuration that makes the client try to decrypt frames that are not
> really for it?
>
this does not happen with the ipw3945 driver but with the iwl3945 so its
either something with this driver or mac80211.
next prev parent reply other threads:[~2007-11-28 14:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 10:02 mac80211 / iwl3945 + dynamic wep (again) drago01
2007-11-25 10:49 ` Johannes Berg
2007-11-25 11:00 ` drago01
2007-11-26 12:14 ` Johannes Berg
2007-11-26 16:04 ` Dan Williams
2007-11-26 16:14 ` Johannes Berg
2007-11-26 16:50 ` drago01
2007-11-27 3:49 ` Jouni Malinen
2007-11-27 17:38 ` Dan Williams
2007-11-27 3:40 ` Jouni Malinen
2007-11-26 14:50 ` dragoran
2007-11-26 15:52 ` Johannes Berg
2007-11-26 16:51 ` drago01
2007-11-26 17:01 ` Johannes Berg
2007-11-27 3:34 ` Jouni Malinen
2007-11-28 14:06 ` drago01 [this message]
2007-11-28 16:50 ` Johannes Berg
2007-11-28 19:45 ` dragoran
2007-11-28 19:47 ` Johannes Berg
2007-11-28 19:50 ` dragoran
[not found] ` <f6ca9fed0801110052ja95e86s9f1842846f0dd8fc@mail.gmail.com>
[not found] ` <1200068256.3861.172.camel@johannes.berg>
[not found] ` <f6ca9fed0801160208x40acfb91p8446298fda9e7726@mail.gmail.com>
2008-01-16 18:38 ` Johannes Berg
2008-01-17 15:38 ` drago01
2008-01-17 15:40 ` Johannes Berg
2007-12-03 10:14 ` Johannes Berg
2007-12-03 11:47 ` dragoran
2007-12-04 6:57 ` dragoran
2007-12-04 7:57 ` dragoran
2007-11-26 15:19 ` Dan Williams
2007-11-26 15:47 ` 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=474D75D9.7070908@gmail.com \
--to=drago01@gmail.com \
--cc=dcbw@redhat.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=yi.zhu@intel.com \
/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).