From: Weedy <weedy2887@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: ath5k past 2.6.30 breaks monitor mode (and thus the aircrack suite)
Date: Sun, 16 May 2010 16:41:58 -0400 [thread overview]
Message-ID: <AANLkTimltZSc8dJPPBCibcGDaOPcQRU_5kSbenIAdi_6@mail.gmail.com> (raw)
Running airodump on ubuntus 2.6.30 kernel works as expected. The
2.6.32 kernel shipped in lucid never sees data packets.
I have narrowed it down to channel hopping. modprobing the driver and
starting mon0 on a fixed channel works as expected, but allowing
airodump to channel hop breaks the interface until the driver is
reset.
I wrote a script to download and build compat wireless starting from
2009-01-01 (granted everything fails until half way through october),
but every version that is successfully installed also show the same
bug.
Further instructions welcome.
next reply other threads:[~2010-05-16 20:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 20:41 Weedy [this message]
2010-05-16 21:49 ` ath5k past 2.6.30 breaks monitor mode (and thus the aircrack suite) 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
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=AANLkTimltZSc8dJPPBCibcGDaOPcQRU_5kSbenIAdi_6@mail.gmail.com \
--to=weedy2887@gmail.com \
--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).