From: Rich Brown <richb.hanover@gmail.com>
To: Richard Smith <smithbone@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Recording RF management info _and_ associated traffic?
Date: Tue, 20 Jan 2015 11:59:41 -0500 [thread overview]
Message-ID: <7B1EA8F0-FCB6-4A37-950F-2558FC751DE8@gmail.com> (raw)
In-Reply-To: <54B5D28A.3010906@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Jan 13, 2015, at 9:20 PM, Richard Smith <smithbone@gmail.com> wrote:
> I'm trying to track down some poor wireless issues we are having at work. At random times the 5Ghz WLANs we have just go to hell.
>
> I've been sniffing in monitor mode which has been quite enlightening there's certainly a lot more going on in the 5Ghz channels than I was expecting.
>
> Monitor mode shows me loads of stuff I didn't know was there but what it doesn't show me is how all that other traffic interacts with the traffic on my ESS.
>
> From what I've been reading it seems like you with most cards you can't grab the 802.11 management info and actual traffic on the network at the same time.
>
> Is this possible with a WNDR3[78]00 CeroWRT (or openWRT) setup?
One of the first things I would do is a Wifi site survey, to look for conflicts between access points/channels, etc. Two recommendations for tools:
MacOSX: WiFi Explorer from Adrian Granados - US$4.99 from the Mac App Store. http://www.adriangranados.com/apps/wifi-explorer
Android: WiFi Analyzer from farproc - Donationware from the Android store. https://sites.google.com/site/farproc/wifi-analyzer
Rich
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2015-01-20 16:59 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 2:20 Richard Smith
2015-01-20 16:59 ` Rich Brown [this message]
2015-01-21 23:40 ` Richard Smith
2015-01-21 23:58 ` David Lang
2015-01-22 9:04 ` Richard Smith
2015-01-22 9:18 ` David Lang
2015-01-22 18:19 ` Richard Smith
2015-01-22 22:09 ` David Lang
2015-01-22 22:55 ` Roman Toledo Casabona
2015-01-24 14:59 ` dpreed
2015-01-24 15:30 ` Kelvin Edmison
2015-01-25 4:35 ` David Lang
2015-01-25 5:02 ` Dave Taht
2015-01-25 5:04 ` Dave Taht
2015-01-25 6:44 ` David Lang
2015-01-25 7:06 ` David Lang
[not found] ` <CAA93jw64KjW-JjLxB3i_ZK348NCyJYSQACFO34MaUsBBWyZ+pA@mail.gmail.com>
2015-01-25 7:59 ` Dave Taht
2015-01-25 9:39 ` David Lang
2015-01-25 15:03 ` Chuck Anderson
2015-01-25 20:17 ` dpreed
2015-01-25 23:21 ` Aaron Wood
2015-01-25 23:57 ` David Lang
2015-01-26 1:51 ` dpreed
2015-01-26 2:09 ` David Lang
2015-01-26 4:33 ` Valdis.Kletnieks
2015-01-26 4:44 ` David Lang
2015-01-27 0:14 ` dpreed
2015-01-27 0:23 ` David Lang
2015-01-26 2:19 ` Dave Taht
2015-01-26 2:43 ` David Lang
2015-01-26 2:58 ` Dave Taht
2015-01-26 3:17 ` dpreed
2015-01-26 3:32 ` David Lang
2015-01-26 3:45 ` Dave Taht
2015-01-27 0:12 ` dpreed
2015-01-27 0:31 ` David Lang
2015-01-27 0:36 ` Dave Taht
2015-01-26 3:19 ` David Lang
2015-01-26 4:25 ` Valdis.Kletnieks
2015-01-26 4:39 ` David Lang
2015-01-26 16:42 ` Valdis.Kletnieks
2015-01-25 8:07 ` Outback Dingo
2015-01-30 16:14 ` Richard Smith
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7B1EA8F0-FCB6-4A37-950F-2558FC751DE8@gmail.com \
--to=richb.hanover@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=smithbone@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