[RFC] Implementing nohwcrypt in wcn36xx

Yeoh Chun-Yeow yeohchunyeow at gmail.com
Fri Mar 28 05:31:50 EDT 2014


> Actually, I have been able to send (software) encrypted frames
> from a STA to an AP, and decrypt them with wireshark and they look
> ok.
>
> The problem in my case is that no encrypted RX frames show up.  I
> suspect this is because firmware sees the protected bit on the frame and
> either drops it, or tries to decrypt it even though there is no key and
> then drops the corrupt frame.  In ath9k/ath5k, the hardware will pass up
> such frames.  I haven't found any setting or filter flag to receive
> these frames yet.

Ya, it is highly possible. Not so sure whether there is kind of raw rx
mode in the firmware.

> I noticed that the header file mentioned AES-128-CMAC, which would
> be great if we could use it, but trying to set these keys doesn't work
> on this hw as far as I can tell:
>
> <7>[   63.536346] wcn36xx: Key: cmd=0x0 algo:0xfac06, id:4, len:16 flags 0x0
> <7>[   63.536376] wcn36xx: KEY: 00000000: 97 d8 58 04 60 c6 ab 0e 8f f4 6c 9c 90 1b 95 64
> <3>[   63.537139] wcn36xx: ERROR hal_set_bsskey response failed err=6

AES CMAC also not support by ath9k. Maybe the best we can is to try
encrypt and decrypt the unicast data frame and let others to be
handled by mac80211.

---
Chun-Yeow



More information about the wcn36xx mailing list