STRUCT CFG80211_GTK_REKEY_DATA(9)

📦 version 7.3.1, in nixpkgs unstable

👑 struct cfg80211_gtk_rekey_data(9) 👑

okay bestie, welcome to the Kernel API Manual ✨ — this is the part where the kernel docs stop being scary and start being kind of iconic. no cap. we're talking about struct cfg80211_gtk_rekey_data, which is literally just a little bundle of rekey data 🎀. that's the whole vibe. it holds the keys, the counter, and the numbers that tell you how big the keys are. iykyk.

💖 NAME 💖

struct cfg80211_gtk_rekey_data — rekey data 🦋

like, that's it. that's the name. "rekey data." it gives exactly what it says on the tin, and honestly? we love a struct that doesn't overpromise. 💅

✨ SYNOPSIS ✨

here's the shape of it, bestie — copy it exactly, don't be out here improvising:

struct cfg80211_gtk_rekey_data {
    const u8 *kek, *kck, *replay_ctr;
    u32 akm;
    u8 kek_len, kck_len;
 };

so real — three pointers (kek, kck and replay_ctr, all const u8 * and all declared on one line together, main character energy 🌟), then a u32 akm, then two u8s: kek_len and kck_len. that's the whole struct. she's compact. she's efficient. she ate. 🔥

🌸 Members 🌸

okay now the fun part — let's meet the members one by one, no member left behind 🫶

  • kek — the key encryption key 💜 and yes, it's kek_len bytes long. the length field tells you how much of it is real, so like, don't go reading past it, bestie 😭
  • kck — the key confirmation key 🎀 and it is kck_len bytes. same deal as above — the length field is the moment of truth.
  • replay_ctr — the replay counter ⭐ and this one is NL80211_REPLAY_CTR_LEN bytes. note that's a named constant, not a number, so don't go making up your own size, okay? 🙈
  • akm — the akm 👑 which is specified as (oui, id). that's the format, that's the whole description, we're not adding extra lore here, that's just what it is.
  • kek_len — length of kek 💅 (yes, of the kek, the key encryption key up there. it's giving "these two are a package deal").
  • kck_len — length of kck 🌈 (same situation, but for the key confirmation key. they match, they're a set, it's cute).

aaand that's part one, bestie — we're not done yet, so don't go anywhere 💖 more coming right up 🌸

✨ SEE ALSO ✨

okay so you just read about struct cfg80211_gtk_rekey_data and now you're like "who else is in this friend group" — valid, obsessed with the curiosity 💅. Everything below lives in the kernel file ./include/net/cfg80211.h, and every single one is a (9) page you can go read next. No gatekeeping here bestie, it's giving full tour of the neighborhood 🫶.

  • Kernel file ./include/net/cfg80211.h
  • Introduction(9)
  • Device registration(9)

Then we get into the channel/rate/bss girlies, and honestly they ate:

🎀 Actions and configuration

this whole section is the main-character energy zone, no cap — config stuff goes hard ✨

🦋 Scanning and BSS list handling

scanning era!! lowkey my fave chapter, it's so thorough 💖

  • Scanning and BSS list handling(9)
  • struct cfg80211_ssid(9)
  • struct cfg80211_scan_info(9)
  • struct cfg80211_scan_6ghz_params(9)
  • struct cfg80211_scan_request(9)
  • struct cfg80211_match_set(9)
  • struct cfg80211_sched_scan_plan(9)
  • struct cfg80211_bss_select_adjust(9)
  • struct cfg80211_sched_scan_request(9)
  • enum cfg80211_signal_type(9)
  • struct cfg80211_inform_bss(9)
  • struct cfg80211_bss_ies(9)
  • struct cfg80211_bss(9)
  • ieee80211_bss_get_elem(9)
  • ieee80211_bss_get_ie(9)
  • struct cfg80211_auth_request(9)
  • struct cfg80211_assoc_link(9)
  • struct cfg80211_ml_reconf_req(9)
  • enum cfg80211_assoc_req_flags(9)
  • struct cfg80211_assoc_request(9)
  • struct cfg80211_deauth_request(9)
  • struct cfg80211_disassoc_request(9)
  • struct cfg80211_ibss_params(9)
  • struct cfg80211_bss_selection(9)
  • struct cfg80211_connect_params(9)
  • enum cfg80211_connect_params_changed(9)
  • enum wiphy_params_flags(9)
  • struct cfg80211_pmksa(9)
  • struct cfg80211_pkt_pattern(9)
  • struct cfg80211_wowlan_tcp(9)
  • struct cfg80211_wowlan(9)
  • struct cfg80211_coalesce_rules(9)
  • struct cfg80211_coalesce(9)
  • struct cfg80211_wowlan_nd_match(9)
  • struct cfg80211_wowlan_nd_info(9)
  • struct cfg80211_wowlan_wakeup(9)
  • struct cfg80211_update_ft_ies_params(9)
  • struct cfg80211_mgmt_tx_params(9)
  • struct cfg80211_dscp_exception(9)
  • struct cfg80211_dscp_range(9)
  • struct cfg80211_qos_map(9)

🌸 Neighbor Awareness Networking (NAN)

NAN girlies rise 🧚 — genuinely such a cute name for a protocol, iykyk.

  • Neighbor Awareness Networking (NAN)(9)
  • struct cfg80211_nan_band_config(9)
  • struct cfg80211_nan_conf(9)
  • struct cfg80211_nan_channel(9)
  • struct cfg80211_nan_local_sched(9)
  • struct cfg80211_nan_peer_map(9)
  • struct cfg80211_nan_peer_sched(9)
  • enum cfg80211_nan_conf_changes(9)
  • struct cfg80211_nan_func_filter(9)
  • struct cfg80211_nan_func(9)
  • struct cfg80211_pmk_conf(9)
  • struct cfg80211_external_auth_params(9)
  • struct cfg80211_ftm_responder_stats(9)
  • struct cfg80211_pmsr_ftm_result(9)
  • struct cfg80211_pmsr_result(9)
  • struct cfg80211_pmsr_ftm_request_peer(9)
  • struct cfg80211_pmsr_request_peer(9)
  • struct cfg80211_pmsr_request(9)
  • struct cfg80211_update_owe_info(9)
  • struct mgmt_frame_regs(9)
  • struct cfg80211_ops(9)
  • enum wiphy_flags(9)
  • struct ieee80211_iface_limit(9)
  • struct ieee80211_iface_combination(9)
  • enum wiphy_wowlan_support_flags(9)
  • struct wiphy_wowlan_support(9)
  • struct wiphy_coalesce_support(9)
  • enum wiphy_vendor_command_flags(9)
  • enum wiphy_opmode_flag(9)
  • struct sta_opmode_info(9)
  • struct wiphy_vendor_command(9)
  • struct wiphy_iftype_ext_capab(9)
  • cfg80211_get_iftype_ext_capa(9)
  • struct cfg80211_pmsr_capabilities(9)
  • struct wiphy_iftype_akm_suites(9)
  • struct wiphy_radio_cfg(9)
  • struct wiphy_radio_freq_range(9)
  • struct wiphy_radio(9)
  • enum wiphy_nan_flags(9)
  • struct wiphy_nan_capa(9)

👑 the wiphy family

the wiphy pages are literally the royal family of this header, periodt 👑

⭐ Utility functions

the little helpers that carry the whole operation fr fr ⭐

💜 Data path helpers

data go zoom, headers go slice, we love to see it 💜

🌈 Regulatory enforcement infrastructure

regulatory content!! this is where the rules live and they are NOT optional bestie 🌈

Then the notification squad — these are the ones that tell the rest of the world something happened, and honestly they're so underrated:

🔥 RFkill integration

turning radios off and on, the original "touch grass" button 🔥

Vendor commands

vendor stuff, aka the "we made our own API and it slays" corner 💅

Test mode

test mode, for when you wanna poke stuff and see what happens 🧪 (not me poking stuff 🙈)

🍓 the connect / roam / mgmt besties

connection life cycle girlies, from hello to bye, they have a page for literally every moment 🍓

🎀 CQM + radar + the random one-offs

quality monitoring notification crew, plus some truly chaotic sounding ones (spurious frame?? unexpected 4addr frame?? iconic names ngl) 😭

okay that's literally the whole list, all 359 of them accounted for, you're so welcome bestie 🫶✨ — and yes cfg80211_gtk_rekey_notify(9) is in there, which is very much your struct's moment to shine 👑

...and it keeps going, bestie 😭 the SEE ALSO list on this thing is literally a phone book, so let's just get through it together, hand in hand 🫶 every single one of these is a real page you can pull up:

like okay the conversion girlies are all here 💅 and we're still going:

not the register/unregister duo 😭 anyway:

feature flags, but make it fashion 👑

the NAN squad showed up and they brought friends 💖

color change notifs: started, aborted, AND finished — she's thorough, we stan 🌈

debugfs read AND write, because bestie needs both sides of the story 📖

and that's the list, we made it, nobody panic 🎉 last three are the S1G freq girlies plus the incumbent signal notif, iconic lineup, no notes.

so yeah, that's the whole page, start to finish 💜 if you forgot what any of these do, that's literally what the cross-references are for — go click through, iykyk.

real talk though: this index entry was served fresh from ./include/net, with an October 2026 date stamp on it, and it's filed under struct cfg80...k_rekey_data(9) in the Kernel API Manual. so if you're citing it, that's the receipts 🧾

k byeee, go write some good driver code, and remember: read the docs before you ship it ✨🌸💅

📦 where this page comes from