From: Roger James <roger@beardandsandals.co.uk>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc - Netgear WNDA3200 - monitor mode
Date: Mon, 21 Mar 2016 21:28:12 +0000 [thread overview]
Message-ID: <56F0676C.7040905@beardandsandals.co.uk> (raw)
Hi,
I am trying to use a Netgear WNDA3200 usb dongle plugged into a box
running Ubuntu 15.10 to monitor a WPA2_PSK encrypted network. This stick
uses the AR7010+AR9280 chipsets. For the particular problem I am
investigating I need to as much of the traffic on the channel as I can.
However I seem to miss almost all of the unicast traffic. I have come
across this problem many times before on other wireless chipsets. I was
hoping the Atheros would be different. I can see unicast 802.11
management traffic but not protected unicast data/qos data frames. I
have hacked the driver to give me the current filter settings via
debugfs and this is what I see.
RXFILTER: 0xc03f UCAST MCAST BCAST CONTROL BEACON PROM PSPOLL
MCAST_BCAST_ALL
Which looks OK to me. I have also checked that all the packets seen by
driver make it up to user level.
Is this expected behaviour?
Is this something to do with htc USB chipset?
Is this something to do with a Netgear customisation?
Has anyone else seen this kind of behaviour?
Is there any way round it?
Help!! This is driving me nuts. I have done so many tests with this and
other adapters that I have lost the plot.
I have a whole slew of tests and results available on request. But I
won't clutter the list with them.
Roger
next reply other threads:[~2016-03-21 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 21:28 Roger James [this message]
2016-03-22 5:40 ` [ath9k-devel] ath9k_htc - Netgear WNDA3200 - monitor mode Janusz Dziedzic
2016-03-22 6:13 ` Oleksij Rempel
-- strict thread matches above, loose matches on Subject: below --
2016-03-22 16:17 Roger James
2016-03-22 16:19 Roger James
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=56F0676C.7040905@beardandsandals.co.uk \
--to=roger@beardandsandals.co.uk \
--cc=ath9k-devel@lists.ath9k.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 read-only IMAP folder(s) and NNTP newsgroup(s).