[RFC] Implementing nohwcrypt in wcn36xx

Yeoh Chun-Yeow yeohchunyeow at gmail.com
Thu Mar 27 22:53:44 EDT 2014


> Mgmt frames, mesh peering frames work fine, we're able to peer,
> exchange crypto materials (and it looks like the same key is derived
> on both ends)-- but when it comes time to actually send data, nothing
> goes out.

I think that the we should set the dpu_ne to 1 and fool the firmware
to treat our data frame as non-encrypted one.

But if this is not working, then there is possibility that the
firmware has inspecting the frame control field and treating it as
encrypted frame. But since we have not set any key on data frame, the
firmware has decided to drop this. Anyone familiar with the firmware
can comment on this?

Also, if you try the STA mode connected to an AP with nohwcrypt set to
1 or without, is this working?

The work around that I can think of, is dropping the nohwcrypt and set
the key for data frame (HW encryption/decryption). But remain the
handling of management frame (encryption/decryption) to mac80211.
Follow the way ath9k is doing.

----
Chun-Yeow



More information about the wcn36xx mailing list