* Fail to Capture QOS data packets in Monitoring mode - QCA988x
@ 2016-07-26 1:43 sdhrtht
2016-07-26 2:07 ` Raj Joshi
0 siblings, 1 reply; 3+ messages in thread
From: sdhrtht @ 2016-07-26 1:43 UTC (permalink / raw)
To: ath10k
ath10k monitor failing to capture data packets with WMM enabled on AP.
AP Status: (when no QOS data Packets. MGMT and CTRL Packets are able to
captured)
1) 0x03 (3) - Secondary channel is below Primary
2) 1 - any Channel width in secondary channel width
3) 1 - Use of RIFS permitted
4) 0x02 - Only HT STAs in the BSS, however there exists at least on 20Mhz
STA
5) 0 - all Associated HT STAs are greenfield capable
Tested with latest CT and non-CT firmware's.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Fail to Capture QOS data packets in Monitoring mode - QCA988x
2016-07-26 1:43 Fail to Capture QOS data packets in Monitoring mode - QCA988x sdhrtht
@ 2016-07-26 2:07 ` Raj Joshi
2016-07-26 3:12 ` sudheer thota
0 siblings, 1 reply; 3+ messages in thread
From: Raj Joshi @ 2016-07-26 2:07 UTC (permalink / raw)
To: sdhrtht; +Cc: ath10k
Hi,
The following may not necessarily be your case. But since you
mentioned MGMT and CTRL packets are captured and not QoS data packets,
I observed a similar behavior when my configuration was as below:
* Sender: Operating 80Mhz dynamic channel width (secondary channel
either above or below primary channel, doesn't matter)
* Sniffer: Operating on 80MHz width. However, the sniffer's primary
channel doesn't overlap with the sender's primary channel; basically
they have different primary channels.
It is necessary that the primary channels of the sender and the
sniffer match. Otherwise, the sniffer is able to only see the non-HT
duplicate frames sent by the sender. This is because those frames are
sent on all the four 20MHz channels, one of which is your sniffer's
primary channel.
I am not sure if the greenfield configuration could be a culprit here.
But you might want to check the above first :)
Cheers,
Raj Joshi
On Tue, Jul 26, 2016 at 9:43 AM, sdhrtht <sdhrtht@outlook.com> wrote:
> ath10k monitor failing to capture data packets with WMM enabled on AP.
>
> AP Status: (when no QOS data Packets. MGMT and CTRL Packets are able to
> captured)
> 1) 0x03 (3) - Secondary channel is below Primary
> 2) 1 - any Channel width in secondary channel width
> 3) 1 - Use of RIFS permitted
> 4) 0x02 - Only HT STAs in the BSS, however there exists at least on 20Mhz
> STA
> 5) 0 - all Associated HT STAs are greenfield capable
>
> Tested with latest CT and non-CT firmware's.
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Fail to Capture QOS data packets in Monitoring mode - QCA988x
2016-07-26 2:07 ` Raj Joshi
@ 2016-07-26 3:12 ` sudheer thota
0 siblings, 0 replies; 3+ messages in thread
From: sudheer thota @ 2016-07-26 3:12 UTC (permalink / raw)
To: Raj Joshi, ath10k@lists.infradead.org
Went through same path and verified with COMMVIEW on primary and secondary channels.
on the other hand, surprisingly Qos packets appears when there another devices associates with AP and disappears when it disconnects. only greenfield mode is disabled during the transition when second STA association happens.
----------------------------------------
> From: rajjoshi@comp.nus.edu.sg
> Date: Tue, 26 Jul 2016 10:07:45 +0800
> Subject: Re: Fail to Capture QOS data packets in Monitoring mode - QCA988x
> To: sdhrtht@outlook.com
> CC: ath10k@lists.infradead.org
>
> Hi,
>
> The following may not necessarily be your case. But since you
> mentioned MGMT and CTRL packets are captured and not QoS data packets,
> I observed a similar behavior when my configuration was as below:
> * Sender: Operating 80Mhz dynamic channel width (secondary channel
> either above or below primary channel, doesn't matter)
> * Sniffer: Operating on 80MHz width. However, the sniffer's primary
> channel doesn't overlap with the sender's primary channel; basically
> they have different primary channels.
>
> It is necessary that the primary channels of the sender and the
> sniffer match. Otherwise, the sniffer is able to only see the non-HT
> duplicate frames sent by the sender. This is because those frames are
> sent on all the four 20MHz channels, one of which is your sniffer's
> primary channel.
>
> I am not sure if the greenfield configuration could be a culprit here.
> But you might want to check the above first :)
>
> Cheers,
> Raj Joshi
>
>
> On Tue, Jul 26, 2016 at 9:43 AM, sdhrtht <sdhrtht@outlook.com> wrote:
>> ath10k monitor failing to capture data packets with WMM enabled on AP.
>>
>> AP Status: (when no QOS data Packets. MGMT and CTRL Packets are able to
>> captured)
>> 1) 0x03 (3) - Secondary channel is below Primary
>> 2) 1 - any Channel width in secondary channel width
>> 3) 1 - Use of RIFS permitted
>> 4) 0x02 - Only HT STAs in the BSS, however there exists at least on 20Mhz
>> STA
>> 5) 0 - all Associated HT STAs are greenfield capable
>>
>> Tested with latest CT and non-CT firmware's.
>>
>>
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-07-26 3:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-07-26 1:43 Fail to Capture QOS data packets in Monitoring mode - QCA988x sdhrtht
2016-07-26 2:07 ` Raj Joshi
2016-07-26 3:12 ` sudheer thota
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox