QosControl missing in eapol key exchanging message

QosControl missing in eapol key exchanging message

[Shu, Nick]

Hi, Group:
I'm using a mini PICe wifi AC NIC & ath10k driver to connect to a Cisco AP. Doing a WPA-PSK authentication that has a 4 way handshake.
When I use wireshark to decode the captured wifi message (Qos Key message 2of 4 is from Sta to AP), I noticed that QoS Control section (0x0007) missing in header, that caused wireshark to not be able to decode the message.
Does anybody knows about this? Any particular reason? Does this violate the spec for message building?

Thanks!
Nick Shu
Spirent Communications e-mail confidentiality.
------------------------------------------------------------------------
This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system.

Spirent Communications plc
Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.
Tel No. +44 (0) 1293 767676
Fax No. +44 (0) 1293 767677

Registered in England Number 470893
Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom.

Or if within the US,

Spirent Communications,
27349 Agoura Road, Calabasas, CA, 91301, USA.
Tel No. 1-818-676- 2300

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QosControl missing in eapol key exchanging message

[Michal Kazior]

On 20 February 2015 at 15:20, Shu, Nick <Nick.Shu@spirent.com> wrote:
> Hi, Group:
> I'm using a mini PICe wifi AC NIC & ath10k driver to connect to a Cisco AP. Doing a WPA-PSK authentication that has a 4 way handshake.
> When I use wireshark to decode the captured wifi message (Qos Key message 2of 4 is from Sta to AP), I noticed that QoS Control section (0x0007) missing in header, that caused wireshark to not be able to decode the message.
> Does anybody knows about this? Any particular reason? Does this violate the spec for message building?

I assume you started wireshark on host with ath10k. In that case
packets the machine transmits will be mangled. The reason is ath10k
needs to strip the QoS Control from each QoS Data frame because
firmware expects the frame in the so called "Native Wifi" format and
QoS is delivered out-of-band (as meta information in Tx command).

I guess this could be a little improved by stripping the QoS Data bit
from Frame Type so that wireshark can decode frames properly at the
cost of not knowing which frames were sent as QoS and non-QoS anymore.


Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k