From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Wunderlich <simon.wunderlich@openmesh.com>,
Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: linux-wireless@vger.kernel.org,
Benjamin Berg <benjamin@sipsolutions.net>
Subject: Re: [PATCH] mac80211: Allow multiple listeners for management frames.
Date: Tue, 14 Mar 2017 15:13:12 +0100 [thread overview]
Message-ID: <1489500792.10872.13.camel@sipsolutions.net> (raw)
In-Reply-To: <3029516.gVNlmVZjU3@prime> (sfid-20170314_151031_045293_89F882D3)
On Tue, 2017-03-14 at 15:10 +0100, Simon Wunderlich wrote:
> On Tuesday, March 14, 2017 3:06:35 PM CET Sven Eckelmann wrote:
> > On Dienstag, 14. März 2017 14:51:01 CET Johannes Berg wrote:
> > [...]
> >
> > > I'm not sure I mentioned it to him, or even remembered it when we
> > > were
> > > discussing it, but I don't think this patch is a good idea, at
> > > least
> > > for action frames.
> >
> > [...]
> >
> > > If you restrict it to non-action I can live with it, but I don't
> > > know
> > > what you really want to do with this.
> >
> > I think he required it only for probe requests.
Similar situation for probe requests though - who answers them? :-)
Though at least in that case the kernel doesn't care (unlike in the
action frame case) since it never does.
> The idea was to grab probe requests from userspace with a program
> running next to hostapd.
I guess there are some efficiency problems with that right now, but a
monitor mode interface should work just as well. Perhaps we can allow
attaching a BPF program to a monitor mode interface, and run that
without cloning the SKB etc.?
johannes
next prev parent reply other threads:[~2017-03-14 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 9:34 [PATCH] mac80211: Allow multiple listeners for management frames Sven Eckelmann
2017-03-14 13:51 ` Johannes Berg
2017-03-14 14:06 ` Sven Eckelmann
2017-03-14 14:10 ` Simon Wunderlich
2017-03-14 14:13 ` Johannes Berg [this message]
2017-03-14 14:21 ` Sven Eckelmann
2017-03-14 14:27 ` 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=1489500792.10872.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benjamin@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=simon.wunderlich@openmesh.com \
--cc=sven.eckelmann@openmesh.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).