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@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
