STRUCT CFG80211_RX_ASSOC_RESP_DATA(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay bestie, this is the cfg80211_rx_assoc_resp_data(9) page from the Kernel API Manual, and the whole vibe is literally:

struct cfg80211_rx_assoc_resp_data — association response data 💅

✨ SYNOPSIS ✨

here's the struct in all its exact, character-for-character glory — no cap, don't let the nested bits scare you 🫶

struct cfg80211_rx_assoc_resp_data {
    const u8 *buf;
    size_t len;
    const u8 *req_ies;
    size_t req_ies_len;
    int uapsd_queues;
    bool assoc_encrypted;
    const u8 *ap_mld_addr;
    struct {
      u8 addr[ETH_ALEN];
      struct cfg80211_bss *bss;
      u16 status;
    } links[IEEE80211_MLD_MAX_NUM_LINKS];
};

🎀 Members 🎀

okay so every member gets its moment, because they all matter 💖

  • buf — the (Re)Association Response frame, meaning header + body. iconic frame energy ✨
  • len — the length of the frame data. literally just the size, bestie 🎀
  • req_ies — information elements from the (Re)Association Request frame. yes, the request-side IEs are in here too 🦋
  • req_ies_len — the length of the req_ies data. keeping the length bestie close 😌
  • uapsd_queues — bitmap of queues configured for uapsd. same format as the AC bitmap in the QoS info field. lowkey important format detail, don't freehand it 💅
  • assoc_encrypted — indicate if the (re)association exchange is encrypted. just tell us if it's encrypted, periodt 🔥
  • ap_mld_addr — AP MLD address, in case of MLO. MLO besties know 🌈
  • links — per-link information indexed by link ID. use links[0] for non-MLO connections. yes, index zero is doing main character duty for non-MLO 🫶
    • links.bss — the BSS that association was requested with. ownership of the pointer moves to cfg80211 in the call to cfg80211_rx_assoc_resp. like, the pointer's custody situation changes, okay? 🔥
    • links.status — set this (along with a BSS pointer) for links that were rejected by the AP. rejected-link bookkeeping, very demure, very mindful 💀

✨ SEE ALSO ✨

okay so this is the entire extended friend group of cfg80211. literally everyone. i'm not skipping a single name because the whole point of a SEE ALSO is that you can go meet the rest of the family, and you deserve the full contact list — no "you'll figure it out", no ✨mystery✨, periodt. 🫶

heads up: these are all manpage section (9) kernel-API entries, so the (9) stays glued to each name. copy/paste them exactly, bestie.

🎀 the meta pages

  • Kernel file ./include/net/cfg80211.h Introduction(9) — the header file this whole page lives in
  • Device registration(9) — where devices get introduced to the stack

🌸 bands, channels & caps (the hardware-vibes crowd)

💅 actions & configuration (the main-character chapter)

🦋 scanning & BSS list handling (the "who's out there" chapter)

  • Scanning and BSS list handling(9) — the chapter itself, iconic
  • 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_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 + the misc structs (the niche besties)

  • Neighbor Awareness Networking (NAN)(9) — its own whole chapter, we love a specialist
  • 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)

👑 the wiphy core (big main character energy)

🍓 utility functions (the little helpers that ate)

🔥 data path helpers

🌈 regulatory enforcement infrastructure

🌈 internal regulatory db functions

⭐ the scan/BSS/MLME notification crew

💀 RFkill integration

🎀 vendor commands

🧚 test mode

🦋 connect / roam / notify-era besties (the rest of the roster, no one left behind)

and that's genuinely every single one — 358 links of pure "go read this next" energy, not one dropped 💅 lowkey a flex ngl

Okay so the SEE ALSO section keeps going (and going, and going 😭) — honestly the whole squad is here, so let's just run through the list. Every single one of these has its own little page waiting for you, so tap in:

Like, that's a whole friend group of pages, bestie — not a single one of them skipped. 👑 No cap, nothing dropped.

And that's a wrap on struct cfg80...oc_resp_data(9)! 🎀 Go forth and read the docs, you absolute icon. 🌈

This little page lives in ./include/net, in the October 2026 edition of the kernel API manual. Bookmark it, screenshot it, send it to the group chat — it's giving study buddy energy. 💅✨🫶

📦 where this page comes from