From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Janusz Dziedzic <janusz.dziedzic@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: carl9170 - monitor mode TP drop
Date: Mon, 07 May 2012 09:00:30 +0200 [thread overview]
Message-ID: <1336374030.4325.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201205032344.17313.chunkeey@googlemail.com> (sfid-20120503_234452_333071_DDB27FCC)
On Thu, 2012-05-03 at 23:44 +0200, Christian Lamparter wrote:
> > > You see without the BIT set, the hardware won't sent any ACKs
> > > (Not even those which are directed at this interface - which of
> > > course is also bad, or even worse?) and with the BIT set (and if
> > > the HW is in Sniffer Mode) then the hardware acks every frames,
> > > even if they are for a different stations.
> > > So your fix might break someone else's setup.
> >
> > You may want to implement the new monitor-mode-vif-to-driver thing in
> > mac80211 which tells you when you're in *pure* monitor mode.
>
> "the new monitor-mode-vif-to-driver"?
> Do you mean like adding a new IFTYPE flag? Or more like a FIF_* flag
> (probably)? for the "pure" monitor/sniffer mode?
No, see 4b6f1dd6a6faf4ed8d209bbd548e78b15e55aee8
johannes
prev parent reply other threads:[~2012-05-07 7:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 7:41 carl9170 - monitor mode TP drop Janusz Dziedzic
2012-04-20 17:59 ` Christian Lamparter
2012-04-23 4:27 ` Janusz Dziedzic
2012-04-23 6:47 ` Johannes Berg
2012-04-23 17:45 ` Christian Lamparter
2012-04-25 5:28 ` Janusz Dziedzic
2012-04-25 17:28 ` Christian Lamparter
2012-04-25 18:24 ` Janusz Dziedzic
2012-04-25 18:54 ` Christian Lamparter
2012-04-26 7:45 ` Janusz Dziedzic
2012-04-26 18:25 ` Christian Lamparter
2012-05-03 7:58 ` Johannes Berg
2012-05-03 21:44 ` Christian Lamparter
2012-05-07 7:00 ` Johannes Berg [this message]
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=1336374030.4325.2.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chunkeey@googlemail.com \
--cc=janusz.dziedzic@gmail.com \
--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 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.