From: James Cameron <quozl@laptop.org>
To: Tyler Gray <graytfg@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwlwifi intermittent beacon capture in monitor mode?
Date: Fri, 23 Mar 2018 08:20:26 +1100 [thread overview]
Message-ID: <20180322212026.GE27398@us.netrek.org> (raw)
In-Reply-To: <CAEo4QHxp3w=PKJ0jgvLNHarw92Ynt=eZNmoWE8w7ZMf_HP9MGw@mail.gmail.com>
G'day Tyler,
I've seen that kind of behaviour when there are multiple APs with the
same beacon timing, and one or more APs are not backing off. In my
case the beacons were colliding. The times without beacons followed a
regular pattern; based on the variance in CPU oscillator clocks of the
APs. Cooling or heating an AP changed the pattern. Behaviour also
varied across cards; RF sensitivity of a batch of cards follows a
statistical normal distribution, with a bit of warping caused by
manufacturing test rejects.
Have you access to a spectrum analyser? You might check what
transmissions are happening at the same time, on or near 2.457 MHz.
Can you exclude all other APs, e.g. by placing the devices inside a
disconnected microwave oven?
Can you monitor the current of the card with a digital storage
oscilloscope?
Can you watch the beacons with an RF probe and an oscilloscope?
Simplest probe is a diode (axial, bandoleer) with leads cut for a
multiple of 2.457 MHz held in oscilloscope probes within an inch or so
of the card antenna.
With both these last two tests, you may see dips corresponding to
beacon transmissions. If they stop, you know you have a firmware or
software problem.
--
James Cameron
http://quozl.netrek.org/
next prev parent reply other threads:[~2018-03-22 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 20:54 iwlwifi intermittent beacon capture in monitor mode? Tyler Gray
2018-03-22 21:20 ` James Cameron [this message]
2018-03-23 8:17 ` Johannes Berg
2018-03-23 15:02 ` Tyler Gray
2018-03-23 16:26 ` Johannes Berg
2018-03-23 18:28 ` Tyler Gray
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=20180322212026.GE27398@us.netrek.org \
--to=quozl@laptop.org \
--cc=graytfg@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 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).