From: Johannes Berg <johannes@sipsolutions.net>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3] mac80211/cfg80211: report monitor channel in wireless extensions
Date: Thu, 10 Nov 2011 10:32:51 +0100 [thread overview]
Message-ID: <1320917571.3967.17.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CA+XFjirhwYeU2fJJ7ua6XxGyG+oKBK9xhxnjOKZqV8-rN9u6nQ@mail.gmail.com> (sfid-20111110_102934_143930_76429D40)
On Thu, 2011-11-10 at 10:28 +0100, Gábor Stefanik wrote:
> > @@ -1342,6 +1342,9 @@ struct cfg80211_gtk_rekey_data {
> > * doesn't verify much. Note, however, that the passed netdev may be
> > * %NULL as well if the user requested changing the channel for the
> > * device itself, or for a monitor interface.
> > + * @get_channel: Get the current operating channel, should return %NULL if
> > + * there's no single defined operating channel if for example the
> > + * device implements channel hopping for multi-channel virtual interfaces.
>
> Why not return the the channel the radio is tuned to at the moment of
> the request in that case?
Mostly, you won't even know. In many cases the device will switch
internally. And even if you could know, since it's switching many times
per second it'll be completely useless.
Frankly, I think this whole thing is completely useless. IMNSHO aircrack
or whatever tool uses this is brain-dead since radiotap reports the
correct frequency for each frame *anyway*.
johannes
next prev parent reply other threads:[~2011-11-10 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 18:52 [PATCH] mac80211/cfg80211: report monitor channel in wireless extensions Johannes Berg
2011-11-08 18:56 ` Ben Greear
2011-11-08 19:00 ` Johannes Berg
2011-11-08 19:01 ` [PATCH v2] " Johannes Berg
2011-11-09 9:30 ` [PATCH v3] " Johannes Berg
2011-11-10 9:28 ` Gábor Stefanik
2011-11-10 9:32 ` Johannes Berg [this message]
2012-12-22 4:32 ` 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=1320917571.3967.17.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@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).