linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: marco@tampabay.rr.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: carl1970: monitor mode only displaying beacons/probs from APs?
Date: Thu, 05 Mar 2015 12:10:58 +0100	[thread overview]
Message-ID: <3859987.D1VAPy8h72@debian64> (raw)
In-Reply-To: <20150304230225.J5EHX.13935.root@cdptpa-web27>

Hello,

On Wednesday, March 04, 2015 11:02:25 PM marco@tampabay.rr.com wrote:
> Quite a while back after doing an upgrade to the latest (back then)
> compat-wireless, I noticed that I was only seeing beacon,prob requests, and
> the occasional data packet when in monitor mode; which at the time I wrote
> off.  After switching to backports-3.18.1-1 recently, I still see the same
> behavior(on x86 and arm).  I'm sure I'm missing something, but I couldn't
> find any references to this behavior in my search.  I also tried "iw wlanX
> set monitor control otherbss" to no avail.  Switching to a different chipset
> using ath9k-htc showed expected traffic.
> 
> Can anyone point me in the right direction?
maybe. Could it be that you are looking for 802.11n(MCS) data frames?
Because by default, carl9170's monitor mode only catches the legacy 
802.11a/b/g frames. If this is the case, then try setting the right
channel mode (HT20/HT40+/HT40-) when selecting the channel. i.e.:  

# iw dev wlanX set channel Y HT20
# iw dev wlanX set channel Y HT40+

I hope this helps. Otherwise, you could try: 

# iw dev wlanX set monitor [...] fcsfail

and see if you are picking up frames this way. This should work, but you
will be picking up mostly damaged stuff, so some extra frame processing
will be needed to filter out the noise. 

Regards,
  Christian

  reply	other threads:[~2015-03-05 11:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04 23:02 carl1970: monitor mode only displaying beacons/probs from APs? marco
2015-03-05 11:10 ` Christian Lamparter [this message]
2015-03-06  5:20   ` Marco
2015-03-06  9:34     ` wim torfs
2015-03-06 16:12       ` marco
2015-03-06 18:45         ` wim torfs

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=3859987.D1VAPy8h72@debian64 \
    --to=chunkeey@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marco@tampabay.rr.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).