From: Johannes Berg <johannes@sipsolutions.net>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Cc: Steve deRosier <derosier@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Avinash Patil <avinashp@quantenna.com>,
Julian Calaby <julian.calaby@gmail.com>
Subject: Re: [PATCH] iw: add command to register and capture mgmt frames
Date: Mon, 16 Oct 2017 11:24:59 +0200 [thread overview]
Message-ID: <1508145899.10607.30.camel@sipsolutions.net> (raw)
In-Reply-To: <20171016084810.plzog2dtzakra4ae@bars>
On Mon, 2017-10-16 at 11:48 +0300, Sergey Matyukevich wrote:
>
> Well, monitor mode support in qtnfmac is in our todo list for sure.
Sure. I'm saying you don't really need full monitor support at all,
just a pure software construct for this.
> Meanwhile the purpose of the patch was not to implement a full-
> fledged mgmt packet capture. We have monitor mode and mature capture
> tools for that.
Right, and I didn't originally see the patch as such, just that the
discussion (and in particular Julian's suggestion) veered off in that
direction.
> Nevertheless in certain cases it is handy to dump selected types of
> mgmt frames while system is up and running without adding the whole
> monitor overhead. The idea was that NL80211_CMD_REGISTER_FRAME and iw
> are the right tools for that task. Anyway, iw is something like a
> 'swiss-army-knife' tool for various tasks related to
> mac80211/cfg80211 reporting and troubleshooting.
I'd see this particular feature in iw more as a way to debug the
registrations, but whatever you ultimately want to use it for I neither
can nor want to control :-)
> Let me know if you have any objections to implementation details :)
Yeah, I'll need to review it, just need a bit more time for that.
> Then I will resubmit it addressing all the comments. Besides I am
> going to change command name from 'capture' to 'dump' to avoid
> confusion. Finally, I will update commit message adding information
> about unicast nature of those registrations.
Sounds good :)
Do you want to resend before I review it?
johannes
next prev parent reply other threads:[~2017-10-16 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 21:00 [PATCH] iw: add command to register and capture mgmt frames Sergey Matyukevich
2017-10-14 22:15 ` Steve deRosier
2017-10-15 9:51 ` Sergey Matyukevich
2017-10-15 13:41 ` Julian Calaby
2017-10-16 7:26 ` Johannes Berg
2017-10-16 8:48 ` Sergey Matyukevich
2017-10-16 9:24 ` Johannes Berg [this message]
2017-10-16 9:43 ` Sergey Matyukevich
2017-10-16 19:17 ` Igor Mitsyanko
2017-10-17 6:03 ` Johannes Berg
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=1508145899.10607.30.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=avinashp@quantenna.com \
--cc=derosier@gmail.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sergey.matyukevich.os@quantenna.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).