From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
netdev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: netdev level filtering? perhaps pushing socket filters down?
Date: Thu, 16 Mar 2017 23:44:04 +0100 [thread overview]
Message-ID: <1489704244.3930.7.camel@sipsolutions.net> (raw)
In-Reply-To: <58CB1714.8000305@candelatech.com>
> Attach at just above the driver, before it ever gets to
> stations/vdevs, and ignore radiotap headers and/or add special
> processing for metadata like rx-info?
That'd be a different feature, perhaps more like XDP.
There anyway is no radiotap header at that point, but not changing
whether or not it makes it to other virtual interfaces is actually not
what we're looking for here at all.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Ben Greear <greearb-my8/4N5VtI7c+919tysfdA@public.gmane.org>,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: netdev level filtering? perhaps pushing socket filters down?
Date: Thu, 16 Mar 2017 23:44:04 +0100 [thread overview]
Message-ID: <1489704244.3930.7.camel@sipsolutions.net> (raw)
In-Reply-To: <58CB1714.8000305-my8/4N5VtI7c+919tysfdA@public.gmane.org>
> Attach at just above the driver, before it ever gets to
> stations/vdevs, and ignore radiotap headers and/or add special
> processing for metadata like rx-info?
That'd be a different feature, perhaps more like XDP.
There anyway is no radiotap header at that point, but not changing
whether or not it makes it to other virtual interfaces is actually not
what we're looking for here at all.
johannes
next prev parent reply other threads:[~2017-03-16 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 22:33 netdev level filtering? perhaps pushing socket filters down? Johannes Berg
2017-03-16 22:33 ` Johannes Berg
2017-03-16 22:52 ` Ben Greear
2017-03-16 22:44 ` Johannes Berg [this message]
2017-03-16 22:44 ` 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=1489704244.3930.7.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 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.