Page MenuHomeFreeBSD

[net80211] add A-MSDU hardware decap sequence number range checking This is part one of a multi-part series aimed at supporting hardware decap'ed A-MSDU frames. Hardware decap'ed A-MSDU frames have a variety of unfun behaviours: * for now, they...
Needs ReviewPublic

Authored by adrian on Aug 29 2017, 11:22 PM.
Tags
None
Referenced Files
F103087974: D12157.diff
Wed, Nov 20, 7:23 PM
Unknown Object (File)
Tue, Nov 19, 11:06 PM
Unknown Object (File)
Tue, Nov 5, 6:34 AM
Unknown Object (File)
Oct 21 2024, 7:30 AM
Unknown Object (File)
Oct 21 2024, 6:49 AM
Unknown Object (File)
Oct 21 2024, 6:24 AM
Unknown Object (File)
Oct 15 2024, 11:04 PM
Unknown Object (File)
Oct 15 2024, 6:12 PM
Subscribers

Details

Reviewers
avos
Summary

...all pretend to be individual 802.11 frames, with ..

  • .. the same sequence number;
  • .. the same CCMP PN;
  • .. the same TKIP countermeasures, etc;
  • and when they're A-MPDU encap'ed, they /also/ need to be queued together in the same RX slot and then dequeued together as a group so the A-MPDU bits are kept in-order.

So, the stack has to grow support for all of the above.

This is phase 1 - add support for the non A-MPDU path to grow A-MSDU
decap support. I'm still in the middle of testing it, so bear with me,
but I figure it should show up for some (very!) initial testing.

Initial testing: ath10k STA, will setup an ath10k AP for some traffic
exchange.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 11292
Build 11658: arc lint + arc unit

Event Timeline

sys/net80211/ieee80211_input.h
137

Shouldn't state availability check included here as well?