[ath9k-devel] ath9k: Size of A-MPDU

[ath9k-devel] ath9k: Size of A-MPDU

[Mohammed Shafi]

Hi Kamran,

> Is there any field set in the first or the last MPDU in an aggregated
> A-MPDU to show that it is first or the last receptively? If yes do you
> think it can be recovered in the wireshark?
based on my basic understanding, we will set more_aggregation bit cleared for
all descriptors for the last packets, other wise it will be set for
all the descriptors of
other packets., this is for the tx path. ath9k_hw_set_txdesc/ar9003_set_txdesc
 will give more idea.

while for rx path we will check for we have desc info its the first
packet of an aggregation.
and last packet.

don't know whether this can be checked in wireshark also(packet just
before block ack ?).
 Felix/Adrian may have more thoughts


>
> Regards,
> Kamran



-- 
thanks,
shafi

[ath9k-devel] ath9k: Size of A-MPDU

[Adrian Chadd]

Kamran asked me privately about this.

The fields are available in the RX descriptor. The question is whether
there's some default radiotap 802.11 header bits that could be set to
indicate received aggregate boundaries, or whether it should be
stuffed into a radiotap vendor extension header.

I've defined a "FreeBSD Atheros" vendor extension header with the
stuff I need for userland spectral scan and radar; I may extend this a
little bit to include the RX HT fields.

It sure would be nice for ath9k and FreeBSD to use the same radiotap
vendor extension for this stuff... :)




Adrian

On 29 June 2012 00:23, Mohammed Shafi <shafi.wireless@gmail.com> wrote:
> Hi Kamran,
>
>> Is there any field set in the first or the last MPDU in an aggregated
>> A-MPDU to show that it is first or the last receptively? If yes do you
>> think it can be recovered in the wireshark?
> based on my basic understanding, we will set more_aggregation bit cleared for
> all descriptors for the last packets, other wise it will be set for
> all the descriptors of
> other packets., this is for the tx path. ath9k_hw_set_txdesc/ar9003_set_txdesc
>  will give more idea.
>
> while for rx path we will check for we have desc info its the first
> packet of an aggregation.
> and last packet.
>
> don't know whether this can be checked in wireshark also(packet just
> before block ack ?).
>  Felix/Adrian may have more thoughts
>
>
>>
>> Regards,
>> Kamran
>
>
>
> --
> thanks,
> shafi