From: Bruno Randolf <br1@einfach.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Paul Fertser <fercerpav@gmail.com>,
linux-wireless@vger.kernel.org,
"Thomas d'Otreppe" <tdotreppe@gmail.com>,
Richard Farina <sidhayn@gmail.com>,
Maxim Levitsky <maximlevitsky@gmail.com>
Subject: Re: [RFC][PATCH] cfg80211: report monitor interface channel via wext when possible
Date: Mon, 24 Jan 2011 10:10:38 +0900 [thread overview]
Message-ID: <201101241010.38393.br1@einfach.org> (raw)
In-Reply-To: <1295773599.3639.4.camel@jlt3.sipsolutions.net>
On Sun January 23 2011 18:06:39 Johannes Berg wrote:
> On Sat, 2011-01-22 at 03:11 +0300, Paul Fertser wrote:
> > This makes it possible to retrieve the channel for the monitor interface
> > in cases when it can be determined unambigously. Tested with ath5k.
>
> NAK.
>
> http://article.gmane.org/gmane.linux.kernel.wireless.general/61860
> I don't think so -- I don't recall anyone ever asking before ;-)
I definetly want this functionality for my WLAN monitoring tool ("horst" -
http://br1.einfach.org/horst). A similar patch has also been discussed for
aircrack-ng in June 2010 (https://patchwork.kernel.org/patch/103589/).
I understand your point of not wanting to report wrong information, esp when
we have multiple interfaces on different channels - but in most situations for
sniffers etc this is not the case, we just have one monitor interface or one
interface + one monitor interface, in which cases I believe we should be able
to report a channel.
So just for the record: I want it, pretty please! :)
bruno
next prev parent reply other threads:[~2011-01-24 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 0:11 [RFC][PATCH] cfg80211: report monitor interface channel via wext when possible Paul Fertser
2011-01-23 9:06 ` Johannes Berg
2011-01-23 9:41 ` Paul Fertser
2011-01-24 11:47 ` Johannes Berg
2011-01-24 1:10 ` Bruno Randolf [this message]
2011-01-24 7:46 ` Paul Fertser
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=201101241010.38393.br1@einfach.org \
--to=br1@einfach.org \
--cc=fercerpav@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=sidhayn@gmail.com \
--cc=tdotreppe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.