From: drago01 <drago01@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Tomas Winkler <tomasw@gmail.com>
Subject: Re: mac80211 / iwl3945 + dynamic wep (again)
Date: Thu, 17 Jan 2008 16:38:19 +0100 [thread overview]
Message-ID: <478F766B.6030504@gmail.com> (raw)
In-Reply-To: <1200508694.8708.24.camel@johannes.berg>
Johannes Berg wrote:
> Hmm.
>
> Not really very helpful. Do you have the WEP key that was in use at that
> time?
no .. (have not stored it somewhere)
> Also, did the message actually occur during this dump?
>
>
Yes and not only once ;)
> Is there any way to get the FCS of packets up to mac80211 from the
> iwlwifi drivers, or is it already snipped off by the firmware?
>
> Maybe you have a separate device you could capture traffic with?
> Preferably not iwlwifi, it seems to have trouble in monitor mode, at
> least my iwl4965 doesn't really seem to see traffic in foreign BSSes.
>
>
Unfortunately no. I remember you sending a patch "adding proper monitor
mode to iwl4965" .. has this ever been ported to iwl3945 ?
> Could you amend the failing printk to something like:
>
> DECLARE_MAC_BUF(mac1);
> DECLARE_MAC_BUF(mac2);
>
> [...]
>
> printk(KERN_DEBUG "WEP decrypt failed (ICV, A1=%s, A2=%s, seq=%x, wepidx=%d\n",
> print_mac(mac1, hdr->addr1), print_mac(mac2, hdr->addr2),
> le16_to_cpu(hdr->seq_ctrl), keyidx)
>
> Then start a packet capture and wait until the message occurs. Once it
> does, quickly run "iwlist key" as root to know what keys are currently
> in use and send me both the keys and the failing packet.
>
>
Can do this (next week)
> Also, please see if maybe the printk is correlated (in time) with
> rekeying, the wpa_supplicant output (maybe with -dd) should tell you.
>
>
I cannot say for sure now but last time I looked at the wpa_supplicant
-ddd output while this was happening nothing was printed at all. But I
will do this again and let you know.
thx
next prev parent reply other threads:[~2008-01-17 15:37 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
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 [this message]
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=478F766B.6030504@gmail.com \
--to=drago01@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.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).