linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* IBSS and AMSDU on ath10k
@ 2015-09-24 21:50 Ben Greear
  0 siblings, 0 replies; only message in thread
From: Ben Greear @ 2015-09-24 21:50 UTC (permalink / raw)
  To: ath10k, linux-wireless@vger.kernel.org

Hello!

I'm trying to figure out why IBSS with AMSDU breaks on CT firmware (ath10k).

First, I have no idea if it works on any other firmware....

The problem I see is that the first frame of the AMPDU
has a single frame, and it looks fine and is received up the stack.

Subsequent frames in the AMPDU with 2+ subframes look mostly correct
at first glance, but the 'bssid' as decoded by the stack and sniffer
is 00:00:00:00:00:00, so the stack will not accept it.

I am guessing that frames are either really broken on the air, or
the re-assembly in the ath10k driver is broken.

The same systems in managed mode show proper bssid on the AMSDU
frames, so maybe it really is an on-air issue.

My ath10k sniffer might suffer the same problem, so I'm not actually
certain what is on the air.

The ath9k as sniffer cannot seem to decode any AMSDU frames, even
if the IBSS devices are using HT instead of VHT framerates.

I'm curious if anyone has any suggestions as to how this is supposed
to work.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-09-24 21:50 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-24 21:50 IBSS and AMSDU on ath10k Ben Greear

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).