From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Weedy <weedy2887@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: ath5k past 2.6.30 breaks monitor mode (and thus the aircrack suite)
Date: Wed, 26 May 2010 00:59:23 +0200 [thread overview]
Message-ID: <AANLkTimIeTadyAhUuri2P630mpDwmBk4B90RpERLbaFE@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinyGlwqq4xshLU5Ol74p0VfcUXBjBGKXlsB2pMy@mail.gmail.com>
On Tue, May 25, 2010 at 4:53 PM, Bob Copeland <me@bobcopeland.com> wrote:
> 2010/5/25 Weedy <weedy2887@gmail.com>:
>> 2010/5/24 Gábor Stefanik <netrolller.3d@gmail.com>:
>>> 2010/5/25 Weedy <weedy2887@gmail.com>:
>>>> 2010/5/23 Gábor Stefanik <netrolller.3d@gmail.com>:
>>>>> In the meantime, one thing to test: Add a printk of sc->opmode.
>>>>
>>>> May 24 22:04:20 tiny-h4x kernel: [41147.243149] sc->opmode: 02 (over9000 times)
>>>>
>>>> So i'm guessing I did it wrong (I don't know C).
>>>> printk(KERN_NOTICE "sc->opmode: %02x\n", sc->opmode);
>>>>
>>>
>>> No, that is correct, and proves my theory (2 is NL80211_IFTYPE_STATION
>>> - it should be 6 for monitor mode).
>>>
>>> BTW, please use "Reply to all".
>>>
>> gmail got rid of the "Reply to all by default" option :<
>>
>> When you have a patch I will be waiting.
>
> Sorry, I missed this thread somehow. Thanks for the detective
> work and apologies for my stupid goof. Gábor, are you prepping
> a patch? I can fix it if you like.
>
If you can, please fix it - I know what the bug is, but have no solid
idea about a fix.
(The long-term fix of course would be to make mac80211 say
NL80211_IFTYPE_MONITOR for monitor interfaces, but AFAIK it is
impossible or unwanted - Johannes can probably shed more light on
this. One thing is sure: saying NL80211_IFTYPE_STATION when only a
monitor interface is active is wrong; it should be IFTYPE_MONITOR, or
if that is impossible, IFTYPE_INVALID.)
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
next prev parent reply other threads:[~2010-05-25 22:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 20:41 ath5k past 2.6.30 breaks monitor mode (and thus the aircrack suite) Weedy
2010-05-16 21:49 ` Gábor Stefanik
2010-05-17 6:38 ` Weedy
2010-05-17 11:21 ` Gábor Stefanik
[not found] ` <AANLkTikRt1fUgngBQxEoEFe1VDrYVFRAoMSR53et7gxf@mail.gmail.com>
[not found] ` <AANLkTim-A_TWT-flrW88gJGan47Xhm7llyrQE3ehDKU6@mail.gmail.com>
[not found] ` <AANLkTim4zLxIQH2r76WZRh9kNigVNAngcK1d9-Cu65Ag@mail.gmail.com>
2010-05-23 18:12 ` Gábor Stefanik
2010-05-23 18:17 ` Gábor Stefanik
[not found] ` <AANLkTimYeL4KQozuTl4le9WUpObsjwp0YAx7eAYq6MBr@mail.gmail.com>
2010-05-25 2:23 ` Gábor Stefanik
2010-05-25 13:30 ` Weedy
2010-05-25 14:53 ` Bob Copeland
2010-05-25 22:59 ` Gábor Stefanik [this message]
2010-05-26 12:43 ` Bob Copeland
2010-05-26 21:47 ` Weedy
2010-05-27 3:49 ` Richard Farina
2010-05-27 14:31 ` Bob Copeland
2010-05-27 17:40 ` Weedy
2010-05-27 18:31 ` Bob Copeland
2010-05-27 18:41 ` John W. Linville
2010-05-28 3:39 ` Weedy
2010-05-28 18:16 ` Richard Farina
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=AANLkTimIeTadyAhUuri2P630mpDwmBk4B90RpERLbaFE@mail.gmail.com \
--to=netrolller.3d@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=weedy2887@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).