STRUCT CFG80211_UNSOL_BCAST_PROBE_RESP(9)

📦 version 7.3.1, in nixpkgs unstable

💜 struct cfg80211_unsol_bcast_probe_resp — Kernel API Manual

okay bestie, so we're deep in the kernel docs rn — this is from the Kernel API Manual, no big deal, and we're talking about struct cfg80211_unsol_bcast_probe_resp. iconic name, i know. say it three times fast, i dare you 🫶

✨ NAME ✨

struct cfg80211_unsol_bcast_probe_resp — literally the unsolicited broadcast probe response parameters, but specifically for 6GHz 💅 like she's a 6GHz-only girly and she knows it.

🦋 SYNOPSIS 🦋

struct cfg80211_unsol_bcast_probe_resp {
    bool update;
    u32 interval;
    size_t tmpl_len;
    const u8 *tmpl;
 };

look at her. four little fields. absolute main character energy ✨ and yes the closing brace has a lil space before it in the original, we don't judge, we reproduce 💖

🎀 Members 🎀

okay so let's do the member-by-member vibe check, one at a time, no skipping, we're thorough here 👑

  • update — this is a bool, and you set it to true if the feature configuration should be updated. that's it. that's the whole job. she's the "did you actually change anything or are we just vibing" flag 🦋
  • interval — packet interval in TUs. and listen, the maximum allowed is 20 TU, fr fr, exactly as mentioned in IEEE P802.11ax/D6.0 26.17.2.3.2 - AP behavior for fast passive scanning. so don't go over 20, she will not slay if you go over 20 😭
  • tmpl_len — template length. the length. of the template. short and sweet, she said what she said 🌸
  • tmpl — template data for probe response. this is a const u8 * bestie, so it's pointing at bytes you should not be out here mutating 🙈
lowkey a note to self: that 20 TU cap isn't a suggestion, it's the documented max in the spec reference above — keep it in your head before you go writing configs 💀

okay so SEE ALSO is lowkey the most extra section on this whole page — it's the receipts list, every single thing this doc links arms with, and bestie there are so many of them. no cap, we're doing all of them, in order, no skipping 💅

Home base first, because everything below lives under it:

  • 🔍 next up: Scanning and BSS list handling(9), which is basically the "finding wifi" arc:
    • ssid & scan requests: struct cfg80211_ssid(9), struct cfg80211_scan_info(9), struct cfg80211_scan_6ghz_params(9), struct cfg80211_scan_request(9)
    • match sets & sched scans: struct cfg80211_match_set(9), struct cfg80211_sched_scan_plan(9), struct cfg80211_bss_select_adjust(9), struct cfg80211_sched_scan_request(9)
    • bss info: 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)
    • auth / assoc / deauth / disassoc: 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)
    • ibss / bss selection / connect: 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)
    • wowlan & coalesce corner: 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)
    • the rest of this cluster: 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)

and that's the list so far — but it is not the end of the page, so stay with me 💜

okay so the SEE ALSO list for this page does not stop, and honestly? queen behavior. here's the rest of the extended universe — every single one, no skips, no cuts, no "etc." (we don't do that here 🫶):

and that's the whole list, bestie — nobody got left out, nobody got merged, every one of them is exactly where she belongs 💅

this page came out of ./include/net, dated October 2026, and the running header/footer on it reads struct cfg80...t_probe_resp(9) — yeah it's truncated, that's just how the generator does her, don't come for her 😭 anyway go read the kernel source, ily, bye 🎀✨

📦 where this page comes from