From: Tsaixiong <ivycx1992@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Capture A-MPDUs
Date: Fri, 24 Oct 2014 08:58:47 +0000 (UTC) [thread overview]
Message-ID: <loom.20141024T105805-661@post.gmane.org> (raw)
In-Reply-To: CAN96bqSLZETaTvUsC2-H2ZOjZAT_5sUYoAWTWmYsdxtXy5Tzug@mail.gmail.com
Astrit Zhushi <a.zhushi <at> cs.ucl.ac.uk> writes:
>
> Hi,
> I need to capture aggregate MPDUs between an AP and a client (both running
iwlwifi driver). I have a monitoring node running Atheros AR9300 (MiniPCIe)
card with a monitoring interface setup. The problem is that aggregated data
frames (A-MPDUs) being sent from AP to the client are not being captured at the
monitoring node, only control frames (CTS,BlockAck). Of course, if AP transmits
to the monitoring node then aggregates can be captured.
>
> My question is that is this a hardware limitation? I suspect that the card is
not passing to the driver aggregated frames that are not destined to itself.
Does this has to do with any state the card has to keep for aggregation?
Finally, if that is the case can the card be instructed to pass all aggregated
frames without keeping any state?
>
> I am looking at the number of frames that are aggregated on a typical WLAN.
While this can be inferred by looking at BlockACKs, seeing actual aggregates
would be helpful as a sanity check.
>
> Thanks,
>
> Astrit
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel <at> lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
Dear Astrit
I am confronting with the same problem!Can you give some advice on where I
can capture the control frame in mac80211?I want to confirm the
receiver ,transimitter and duration of next data frame.
Thanks in advance.
Tsaixiong
next prev parent reply other threads:[~2014-10-24 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 9:00 [ath9k-devel] Capture A-MPDUs Astrit Zhushi
2013-08-06 14:01 ` shinnazar
2013-08-06 16:14 ` Astrit Zhushi
2014-10-24 8:58 ` Tsaixiong [this message]
2014-10-24 9:51 ` Kamran Nishat
2014-10-24 11:36 ` Kamran Nishat
2014-10-24 13:27 ` Adrian Chadd
2015-09-11 10:49 ` Astrit Zhushi
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=loom.20141024T105805-661@post.gmane.org \
--to=ivycx1992@gmail.com \
--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 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.