STRUCT CFG80211_FILS_RESP_PARAMS(9)

📦 version 7.3.1, in nixpkgs unstable

💖 struct cfg80211_fils_resp_params 💖

okay bestie, welcome to the Kernel API Manual, section 9 — yes we're in the kernel-API girlies part of the manual, and today's main character is struct cfg80211_fils_resp_params, aka the FILS connection response params. no cap, this one's a lil struct and she's carrying a lot of responsibility 🫶

🌸 NAME 🌸

struct cfg80211_fils_resp_params — FILS connection response params ✨

🦋 SYNOPSIS 🦋

literally the whole vibe, verbatim:

struct cfg80211_fils_resp_params {
    const u8 *kek;
    size_t kek_len;
    bool update_erp_next_seq_num;
    u16 erp_next_seq_num;
    const u8 *pmk;
    size_t pmk_len;
    const u8 *pmkid;
 };

like, that's her. that's the struct. 🎀

👑 Members 👑

okay so let's go member by member, because every single one of these matters and i'm not skipping a single one, periodt 💅

  • kek — the KEK, and it's derived from a successful FILS connection. important: it may be NULL 🙈
  • kek_len — the length of fils_kek in octets. yes bestie, the doc literally spells it fils_kek here, that's exactly what it says, i'm not touching it, iykyk 🍓
  • update_erp_next_seq_num — a Boolean value, and what it's telling you is whether the value sitting in erp_next_seq_num is valid or not. so like, a vibe check for the next field ⭐
  • erp_next_seq_num — the next sequence number to use in the ERP message in FILS Authentication. and listen, this one is special: this value should be specified irrespective of the status for a FILS connection. like, regardless of how the connection went, you still fill this in 🔥
  • pmk — a new PMK, but only if it was derived from a successful FILS connection. and yeah, it may be NULL too 🌈
  • pmk_len — the length of pmk in octets ✨
  • pmkid — a new PMKID if it was derived from a successful FILS connection, or the PMKID used for this FILS connection. either way, heads up: it may be NULL 💜
quick recap bestie: three of these pointers are allowed to be NULL — kek, pmk, and pmkid — and erp_next_seq_num is the one you fill in no matter what the status is. don't forget it, i'm begging 😭

and that's only part 1, there's more coming 👀💖

🌈 SEE ALSO 🌈

okay bestie, buckle up, because this is the part where the manual page just... spills the whole friend group 💅. Everything below is literally the cross-reference list for this page — every single one lives in Kernel file ./include/net/cfg80211.h territory, and every one of them is (9) because that's just how the kernel-doc girlies roll. I'm keeping them in the exact order they were handed to me, no shuffling, no cap. ✨

okay so the reading list does NOT stop, and honestly? this is the part where the SEE ALSO section really pops off 💅 so many icons, one page. grab a snack, we're going through all of them, and no we are not skipping any 🍓

the regulatory + channel girlies first, they're the ones with opinions about where you're allowed to exist

the interface + device + assorted household names

the IE girlies 🎀 splitting, fragmenting, and generally being extra about elements

wakeups, crit protos, and the channel-combination math besties

feature flags and the NAN cinematic universe 🌈 (it has lore, fr)

auth, PMSR, and the "is this even allowed" committee

BSS housekeeping + the color change saga (drama, honestly)

MLO + channel checking, the main character energy section

more NAN (told you, lore), then debugfs and the S1G girlies

and the very last one, saving the best for the end bestie

✨ and that's the whole reading list, bestie — you ate that. this one lives over in ./include/net, it's the October 2026 edition of the struct cfg80..._resp_params(9) page (yes, that's the truncated title, it's giving mysterious), so go forth and cross-reference responsibly 💖🦋👑

📦 where this page comes from