All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Marco Fonseca <marco@tampabay.rr.com>,
	linux-wireless@vger.kernel.org, "Chen,
	Stephen" <scchen@qca.qualcomm.com>
Subject: Re: carl9170: Unintentional transmission in monitor mode?
Date: Thu, 16 Aug 2012 21:34:31 +0200	[thread overview]
Message-ID: <201208162134.32152.chunkeey@googlemail.com> (raw)
In-Reply-To: <1345144855.4665.3.camel@jlt3.sipsolutions.net>

On Thursday, August 16, 2012 09:20:55 PM Johannes Berg wrote:
> On Thu, 2012-08-09 at 21:43 +0200, Christian Lamparter wrote:
> > On Thursday, August 09, 2012 06:54:34 PM Marco Fonseca wrote:
> > > Hello All,
> > > 
> > > I've noticed unexpected transmissions from the AR9170 while in monitor mode
> > > and using tcpdump (and sometimes without tcpdump running).  These
> > > transmissions degrade (pretty significantly) performance of other STA/AP on
> > > the channel (as seen by iperf going from 60mbit/s to almost nill).  As best I
> > > can tell these transmissions never coalesces into an actual frame in the air
> > > (at least not one I'm able to pick up with a second different adapter in
> > > monitor mode).
> > > 
> > > Are there any known reasons/bugs on this?  Is there anyway to completely
> > > silence the transmitter of the AR9170 while still allowing reception?
> > > 
> > yes. <http://www.spinics.net/lists/linux-wireless/msg88896.html>
> > 
> > a solution is described in:
> > <http://www.spinics.net/lists/linux-wireless/msg89279.html>
> > 
> > (iw dev wlanX set monitor none - if I'm not mistaken)
> 
> I've seen this before too -- what flag causes the issue, and why?
Well that would be:
FIF_OTHER_BSS or FIF_PROMISC_IN_BSS

either one of these will set following flags
for the hardware:

AR9170_MAC_RX_CTRL_ACK_IN_SNIFFER
AR9170_MAC_SNIFFER_ENABLE_PROMISC

About the issue, I'm really can't tell w/o schematics
of the hardware. It could be that ACK_IN_SNIFFER is
more of a debug/test flag than a real feature?

(Anyway, I cc'd Stephen. Maybe he knows more)

Regards,
	Chr

  reply	other threads:[~2012-08-16 19:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 16:54 carl9170: Unintentional transmission in monitor mode? Marco Fonseca
2012-08-09 19:43 ` Christian Lamparter
2012-08-10 18:49   ` Marco Fonseca
2012-08-16 19:20   ` Johannes Berg
2012-08-16 19:34     ` Christian Lamparter [this message]
2012-08-17  2:03       ` Chen, Stephen
2012-08-17  2:30         ` Marco Fonseca
2012-08-17  2:59           ` Chen, Stephen
2012-08-17 12:55             ` marco

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=201208162134.32152.chunkeey@googlemail.com \
    --to=chunkeey@googlemail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marco@tampabay.rr.com \
    --cc=scchen@qca.qualcomm.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 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.