How to make software re-calc received frames with bad FCS?

How to make software re-calc received frames with bad FCS?

[Ben Greear]

I'm back to trying to get multiple stations working to same AP
with WPA2 on ath10k.

I tried  doing 'nohwcrypt', but I had no luck with that.  I think
the firmware would require a fair bit of changes to make that happen.

So, a second plan is to just tell the firmware to use hardware crypt
for the VIFs.  This would have a good benefit of offloading the tx
path, at least.

This seems to work for transmit, but on receive, the hardware hash
collides since 2+ stations have same peer (ie, the AP).

I do receive packets, but they are flagged with FCS errors (and I think
there is no re-assembly of ampdu, but I'm not sure how much that matters).

My thought is to somehow flag these packets as needing to be decrypted
by software instead, similar to how the normal nohwcrypt logic works.

Any suggestions for how to go about attempting this?   Maybe
just force remove the CRC failure bit from the status before
passing up the stack?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


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

How to make software re-calc received frames with bad FCS?

[Ben Greear]

I'm back to trying to get multiple stations working to same AP
with WPA2 on ath10k.

I tried  doing 'nohwcrypt', but I had no luck with that.  I think
the firmware would require a fair bit of changes to make that happen.

So, a second plan is to just tell the firmware to use hardware crypt
for the VIFs.  This would have a good benefit of offloading the tx
path, at least.

This seems to work for transmit, but on receive, the hardware hash
collides since 2+ stations have same peer (ie, the AP).

I do receive packets, but they are flagged with FCS errors (and I think
there is no re-assembly of ampdu, but I'm not sure how much that matters).

My thought is to somehow flag these packets as needing to be decrypted
by software instead, similar to how the normal nohwcrypt logic works.

Any suggestions for how to go about attempting this?   Maybe
just force remove the CRC failure bit from the status before
passing up the stack?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com