From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Richard Farina <sidhayn@gmail.com>,
linux-wireless@vger.kernel.org, scchen@qca.qualcomm.com,
linville@tuxdriver.com, marco@tampabay.rr.com,
janusz.dziedzic@gmail.com
Subject: Re: [PATCH] carl9170: fix spurious transmissions in sniffer mode
Date: Wed, 12 Sep 2012 09:09:57 +0200 [thread overview]
Message-ID: <1347433797.4293.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <201209120308.30985.chunkeey@googlemail.com> (sfid-20120912_030846_969448_7F6F8B63)
On Wed, 2012-09-12 at 03:08 +0200, Christian Lamparter wrote:
> Anyway, now the hardware will only react to frames that
> are "directed" (DA matches either the main, or one of
> the 8 vif mac addresses) to it (is this now sane or
> not?).
That's reasonable. A lot of hardware behaves that way, and for many
injection use cases it is actually desired while normal monitoring use
cases aren't really affected. If you'd want to not have this you could
inject with a different MAC address, so it's still fine.
> (BTW: wasn't there once some sort of a "tx ack" control
> interface in mac80211 debugfs path? Does anybody know
> what happend to it?)
It moved into cfg80211/nl80211, but it's only applicable for properly
transmitted QoS frames anyway.
johannes
next prev parent reply other threads:[~2012-09-12 7:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 21:18 [PATCH] carl9170: fix spurious transmissions in sniffer mode Christian Lamparter
2012-09-11 22:03 ` Richard Farina
2012-09-11 23:26 ` Christian Lamparter
2012-09-11 23:46 ` Richard Farina
2012-09-12 1:08 ` Christian Lamparter
2012-09-12 7:09 ` Johannes Berg [this message]
2012-10-13 8:59 ` Christian Lamparter
2012-10-26 18:07 ` Christian Lamparter
2012-10-26 21:03 ` John W. Linville
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=1347433797.4293.2.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chunkeey@googlemail.com \
--cc=janusz.dziedzic@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marco@tampabay.rr.com \
--cc=scchen@qca.qualcomm.com \
--cc=sidhayn@gmail.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).