STRUCT CFG80211_FT_EVENT_PARAMS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

struct cfg80211_ft_event_params β€” FT Information Elements

Ok so real talk, bestie: this is from the Kernel API Manual, section 9 (the header up top literally reads struct cfg8...event_params(9) Kernel API Manual struct cfg8...event_params(9) β€” yes it truncates itself, iconic honestly). It's a struct, it's about FT Information Elements, and we're gonna go through it field by field. No skipping. πŸ’…


🌸 SYNOPSIS 🌸

Here's the whole vibe, exactly as it lives in the kernel:

struct cfg80211_ft_event_params {
    const u8 *ies;
    size_t ies_len;
    const u8 *target_ap;
    const u8 *ric_ies;
    size_t ric_ies_len;
 };

Five members, two of them are lengths, three of them are pointers. It's giving "pair every buffer with its length, always" and honestly? Slay. πŸŽ€


πŸ¦‹ Members πŸ¦‹

  • ies β€” the FT IEs themselves. This is the actual information-element payload, a const u8 * pointing at it. ✨
  • ies_len β€” length of the FT IE in bytes. Yes queen, we track the size. size_t energy. 🌸
  • target_ap β€” the target AP's MAC address. That's the access point you're heading toward, lowkey the whole point of the operation. 🎯
  • ric_ies β€” the RIC IE. A separate pointer, a separate IE, no cap. 🫢
  • ric_ies_len β€” length of the RIC IE in bytes. Every IE gets its own length bestie, that's the rule. πŸ’–
Heads up: ies, target_ap, and ric_ies are all const u8 * and both lengths are size_t. Copy them exactly like that if you're writing code against this β€” don't go improvising types, that's not the vibe. πŸ™ˆ

okay bestie, buckle up β€” this is the part of the page where the kernel just introduces you to everyone it knows. it's giving "wedding seating chart but everyone's a struct." no cap, it's long. every single name here is real and spelled exactly right, so if you go grepping, they'll all be there. πŸ’…

  • The source file itself, the whole reason we're here: ./include/net/cfg80211.h
  • The starter pack: Introduction(9), Device registration(9)

🌸 the band / channel / rate girlies


πŸŽ€ actions & configuration (the main character section fr)


πŸ¦‹ scanning & BSS list handling (the gossip network, literally)

  • 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)
  • the power-save / wowlan crew: 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_gtk_rekey_data(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)

🧚 NAN (Neighbor Awareness Networking β€” yes that's the actual long name, slay)

  • 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)
  • ranging squad: 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), struct wiphy(9)

πŸ’œ the wiphy lifecycle (birth, registration, work queues, the whole arc)


🌈 utility functions (the little helpers that carry the whole friend group)


πŸ”₯ data path helpers


πŸ‘‘ regulatory enforcement infrastructure (the rules girlies)


πŸ’– more BSS & MLME notifications


🫢 RFkill integration


πŸ“ vendor commands & test mode (the wildcard entries)


⭐ connect / roam / station notifs (the drama arc)


and that's the whole SEE ALSO roster β€” 360-ish names and not a single one skipped, iykyk. πŸ’… don't go anywhere, there's still more page coming πŸ¦‹

okay so the SEE ALSO list literally keeps going β€” she's LONG, and every single one of these is a real page you can go pull up, so here's the rest of the squad, no cuts, no skips πŸ’–


and then we hit the NAN section of the reading list, which is giving ✨ whole saga ✨:

back to the general roster, bestie, we're not done yet 🫢:

and yep, more NAN lore, because of course there is πŸ¦‹:

the final stretch, we're so close, hydrate bestie πŸ’…:


aaaand that's the whole reading list, you ate that ngl πŸ‘‘ that's every single cross-reference, nothing dropped, nothing merged, we keep it exactly like the original because that's the whole point, periodt ✨

okay and real talk for a sec β€” this came out of ./include/net and it's dated October 2026, filed under the title struct cfg8...event_params(9). So if you ever gotta cite her, that's where she lives πŸ’– go be iconic with your kernel docs, bestie, ily, bye πŸŽ€πŸŒΈ
πŸ“¦ where this page comes from