ieee80211_get_key_rx_seq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ieee80211_get_key_rx_seq β€” Kernel API Manual, section 9 ✨

hey bestie 🫢 okay so this page is from the Kernel API Manual, section 9, and it's about one very specific little function in mac80211 land. it's not long, but every word is load-bearing, so let's go πŸ’–


🌸 NAME 🌸

ieee80211_get_key_rx_seq β€” get key RX sequence counter πŸ”₯


πŸŽ€ SYNOPSIS πŸŽ€

void ieee80211_get_key_rx_seq (struct ieee80211_key_conf *keyconf , int
tid , struct ieee80211_key_seq *seq );

like, that's the whole vibe check: three args in, nothing out πŸ™ˆ


✨ ARGUMENTS ✨

  • keyconf β€” it's the parameter that got passed along with the set key. iykyk πŸ’…
  • tid β€” the TID 🧚 or -1 for the management frame value (CCMP/GCMP only, no cap on that one). also, heads up: the value on TID 0 is also used for non-QoS frames. and for CMAC, only TID 0 is valid β€” periodt πŸ’€
  • seq β€” the buffer where the sequence data lands. literally just the receiving end of the whole operation πŸ“

πŸ’– DESCRIPTION πŸ’–

so this function is the one that lets a driver retrieve the current RX IV/PNs for the given key. it's giving "hey what's the counter at rn" energy πŸ‘‘

⚠️ but bestie, listen: it must not be called if IV checking is done by the device and not by mac80211. like, that's not a suggestion, that's the rule 🚫

and also note β€” highkey important β€” this function may only be called when no RX processing can be done concurrently. no sneaky parallel stuff while you're in here πŸ™ˆ


πŸ¦‹ SEE ALSO πŸ¦‹

so the kernel file for all of this is ./include/net/mac80211.h, and honestly the cross-reference list is iconic and enormous, so buckle in 🌈

okay that was a lot but we got through it together πŸ«ΆπŸ’–


and that's the whole page, bestie! πŸŽ€ this one came straight out of ./include/net, dated October 2026, in the Kernel API Manual, section 9 β€” ieee80211_get_key_rx_seq(9). go get that sequence counter, you icon πŸ‘‘πŸ’… ✨

πŸ“¦ where this page comes from