From: Andy Green <andy@warmcat.com>
To: Stefan Schweizer <genstef@gentoo.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Monitor mode with RTL8187
Date: Tue, 10 Jul 2007 11:14:23 +0100 [thread overview]
Message-ID: <46935BFF.20800@warmcat.com> (raw)
In-Reply-To: <f6vep6$n3$1@sea.gmane.org>
Stefan Schweizer wrote:
> Andy Green wrote:
>> ifconfig wlan0 down
>>
>> Then after changing the mode, bring it up and set the channel.
>
> why can it not do that automatically when issueing the mode monitor command?
>
> Seems usability has not yet reached wireless configuration - where it is imo
> much needed.
It's really a userspace issue... libpcap could be given the primitives
so tcpdump or whatever can set the mode and bring the interface up.
On the same subject, why is scanning done by a separate app (iwlist)
from iwconfig? Why is scanning specially modal in the stack (or even
worse the device firmware) when there are enough primitives lying around
to do it from userspace? I guess the answer is it got started like that
and now people are using it that way changing is harder.
BTW apropos of nothing let me note that the try #13 injection patches
apply to current wireless-dev with only a single fuzz, and are available
right here:
[PATCH Try#lucky13 1/3] mac80211: Monitor mode radiotap injection docs
http://www.spinics.net/lists/linux-wireless/msg03055.html
[PATCH Try#lucky13 2/3] cfg80211: Radiotap parser
http://www.spinics.net/lists/linux-wireless/msg03056.html
[PATCH Try#lucky13 3/3] mac80211: Monitor mode radiotap-based packet
injection
http://www.spinics.net/lists/linux-wireless/msg03054.html
-Andy
prev parent reply other threads:[~2007-07-10 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 21:51 Monitor mode with RTL8187 Jorge Lucángeli Obes
2007-07-10 5:21 ` Andy Green
2007-07-10 8:07 ` Stefan Schweizer
2007-07-10 8:50 ` Michael Buesch
2007-07-10 23:02 ` Johannes Berg
2007-07-10 10:14 ` Andy Green [this message]
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=46935BFF.20800@warmcat.com \
--to=andy@warmcat.com \
--cc=genstef@gentoo.org \
--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).