From: Bruno Randolf <br1@thinktube.com>
To: Jes Sorensen <Jes.Sorensen@redhat.com>, Bruno Randolf <br1@einfach.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] rtl8xxxu: Enable data frame reception in rtl8xxxu_start
Date: Thu, 22 Oct 2015 08:50:27 +0100 [thread overview]
Message-ID: <56289543.1070008@thinktube.com> (raw)
In-Reply-To: <wrfjoafrrf1s.fsf@redhat.com>
On 10/22/2015 12:13 AM, Jes Sorensen wrote:
> Bruno Randolf <br1@einfach.org> writes:
>> mac80211 documentation says, the ieee80211_ops.start callback "must turn on
>> frame reception (for possibly enabled monitor interfaces.)". If not a single
>> monitor interface does not receive data frames.
>>
>> Similarly we should not change the data reception based on the association
>> state.
>>
>> Signed-off-by: Bruno Randolf <br1@einfach.org>
>> ---
>> drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c | 12 ++----------
>> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> Bruno,
>
> Thanks - I am not 100% convinced about this one. I don't think we should
> tell the firmware to pass up data frames before we have negotiated the
> connection.
>
> It's true that for monitor mode, we need to enable it if all packets
> are requested. Looking at iw there is an option where it only requests
> control packets, and one for all, etc. However for non monitor mode, we
> shouldn't pass all data packets up to the stack, resulting and have
> mac80211 parse them all.
But mac80211 requests us to do so - please see include/net/mac80211.h
line 2576 or
https://www.kernel.org/doc/htmldocs/80211/API-struct-ieee80211-ops.html
I know you are focusing on STA mode at the moment, but
enabling/disabling data reception on association is not correct for most
other modes.
Also don't be afraid of too many frames being passed. In the initial
setting (without a monitor interface) the RCR RCR_ACCEPT_AP bit is not
set and the RCR_CHECK_BSSID_* bits are set as well.
bruno
next prev parent reply other threads:[~2015-10-22 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 21:28 [PATCH] rtl8xxxu: Enable data frame reception in rtl8xxxu_start Bruno Randolf
2015-10-21 23:13 ` Jes Sorensen
2015-10-22 7:50 ` Bruno Randolf [this message]
2015-10-22 13:10 ` Jes Sorensen
2015-10-22 13:22 ` Bruno Randolf
2015-10-22 13:42 ` Jes Sorensen
2015-10-22 13:50 ` Bruno Randolf
2015-10-23 20:31 ` Jes Sorensen
2015-10-23 16:30 ` Larry Finger
2015-10-30 19:32 ` Jes Sorensen
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=56289543.1070008@thinktube.com \
--to=br1@thinktube.com \
--cc=Jes.Sorensen@redhat.com \
--cc=br1@einfach.org \
--cc=linux-wireless@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 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).