dynamic vlan with ath10k not working - regression

Michal Kazior michal.kazior at tieto.com
Thu May 19 23:26:32 PDT 2016

On 19 May 2016 at 13:45, Guenther Kelleter <Guenther.Kelleter at devolo.de> wrote:
> Hi
>> -----Original Message-----
>> From: Hostap [mailto:hostap-bounces at lists.infradead.org] On Behalf Of M. Braun
>> Sent: Sunday, May 15, 2016 4:45 PM
>> To: hostap at lists.infradead.org
>> Subject: Re: dynamic vlan with ath10k not working - regression
>> Am 13.05.2016 um 13:46 schrieb Guenther Kelleter:
>> > Let me sum up what I did understand so far:
>> > ...
>> > Is this correct?
>> Yes.
>> To be more precise, that "base" interface is per BSS and has type "AP",
>> but that does not really make a difference here.
> Ah, but isn't this exactly the difference that matters here?
> According to a comment in mac80211 an AP_VLAN interface is not represented by a vdev of the driver. And a key cannot be installed for a VLAN. Does AP_VLAN encryption have to be handled in software? But the SW_CRYPTO_CONTROL flag somehow prevents SW-crypto for ath10k.
> How is this VLAN encryption gonna work at all when for an AP_VLAN neither HW nor SW- crypto are supported?
> I don't get it.

Some drivers (i.e. ath10k in this case) don't use real 802.11 frames
when talking to device firmware hence it is impossible to pass through
things like IV and MIC unless both FW and HW fully support given
crypto mode.

See: https://git.kernel.org/cgit/linux/kernel/git/kvalo/ath.git/commit/?id=fa7e1fbcb52cc9efab394526a566d80fb31529bb

What you can do is to try using raw mode in ath10k (I think recent
10.2.4.x should do fine) by playing around with "cryptmode" and
"rawmode" ath10k_core module parameters.

Be vary that this will impact performance (both airtime efficiency and
CPU consumption for various reasons).


More information about the Hostap mailing list