STRUCT WIPHY_IFTYPE_EXT_CAPAB(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct wiphy_iftype_ext_capab β€” kernel API manual, bestie edition

okay so we're diving into struct wiphy_iftype_ext_capab(9) from the Kernel API Manual. yes it's a long one, yes we're doing it in parts, and yes you're gonna get it. buckle up πŸŽ€


✨ NAME ✨

struct wiphy_iftype_ext_capab β€” extended capabilities per interface type. that's it, that's the whole vibe. it's the struct that says "hey, this interface type can do these extra things" πŸ¦‹


🌸 SYNOPSIS 🌸

here's the whole thing, exactly as it lives, no notes:

struct wiphy_iftype_ext_capab {
    enum nl80211_iftype iftype;
    const u8 *extended_capabilities;
    const u8 *extended_capabilities_mask;
    u8 extended_capabilities_len;
    u16 eml_capabilities;
    u16 mld_capa_and_ops;
    u16 ext_mld_capa_and_ops;
 };

look at her. seven fields. main character energy fr fr πŸ‘‘


🫢 Members 🫢

okay now the part where we meet everyone individually. it's giving group chat introductions πŸ’–

  • iftype β€” the interface type. literally just which kind of interface we're talking about ✨
  • extended_capabilities β€” the extended capabilities the driver supports. and listen, additional capabilities might be supported by userspace too, so don't assume the driver's list is the whole story. these are the 802.11 extended capabilities (the "Extended Capabilities element") and they're in the same format as they are in the information element. for the defined fields, go look at IEEE Std 802.11-2012 8.4.2.29 β€” yes it's a real citation, yes you should actually check it πŸ“š
  • extended_capabilities_mask β€” the mask of the valid values. slay πŸ’…
  • extended_capabilities_len β€” the length of the extended capabilities. that's the whole job. respect 🫑
  • eml_capabilities β€” EML capabilities (for MLO). 🌈
  • mld_capa_and_ops β€” MLD capabilities and operations (for MLO). πŸ”₯
  • ext_mld_capa_and_ops β€” Extended MLD capabilities and operations (for MLO). ⭐
no cap: if you see "for MLO" three times in a row like that, it's not a typo, it's just how this struct rolls. the MLO fields are MLO fields, periodt 🧚

and that's the struct and all its members, fully accounted for, nothing skipped, nothing summarised away πŸ’œ

✨ SEE ALSO ✨

okay bestie, deep breath. this is the part of the page where it name-drops literally everyone it knows, and i mean everyone β€” no cap, we're not cutting a single one, because every single reference here is somebody's hyperfixation and they'd notice 😭 so buckle up, it's a long crew, and we're going through it in order πŸ’…

that first chunk is giving "everything you ever wanted to know about caps and bands" energy 🌸 and ngl the double-underscore one up there, _ieee80211_set_sband_iftype_data(9), is lowkey the main character of that friend group.


bestie the chandef squad alone could fill a group chat πŸ’€ but honestly? iconic. obsessed with how many of them are just asking "is this channel even valid tho".

  • struct cfg80211_crypto_settings(9), struct cfg80211_mbssid_config(9), struct cfg80211_mbssid_elems(9), struct cfg80211_rnr_elems(9), struct cfg80211_beacon_data(9), struct cfg80211_acl_data(9), struct cfg80211_fils_discovery(9), struct cfg80211_unsol_bcast_probe_resp(9), struct cfg80211_s1g_short_beacon(9)
  • struct cfg80211_ap_settings(9), struct cfg80211_ap_update(9), struct cfg80211_csa_settings(9), struct cfg80211_color_change_settings(9), struct iface_combination_params(9)
  • enum station_parameters_apply_mask(9), struct sta_txpwr(9), struct link_station_parameters(9), struct link_station_del_parameters(9), struct cfg80211_ttlm_params(9), struct station_parameters(9), struct station_del_parameters(9)
  • enum cfg80211_station_type(9), cfg80211_check_station_change(9), enum rate_info_flags(9), enum rate_info_bw(9), struct rate_info(9), enum bss_param_flags(9), struct sta_bss_parameters(9)
  • struct cfg80211_txq_stats(9), struct cfg80211_tid_stats(9), struct link_station_info(9), struct station_info(9), struct cfg80211_sar_sub_specs(9), struct cfg80211_sar_specs(9), struct cfg80211_sar_freq_ranges(9), struct cfg80211_sar_capa(9), cfg80211_get_station(9)
  • enum monitor_flags(9), enum mpath_info_flags(9), struct mpath_info(9), enum wiphy_bss_param_flags(9), struct bss_parameters(9), struct mesh_config(9), struct mesh_setup(9), struct ocb_setup(9), struct ieee80211_txq_params(9)

the station + mesh + sar era of the list, we love a versatile queen 🫢 seriously though, every one of these is a real page you might need, so don't skip the "boring" looking ones.


  • 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_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)

scanning era!! auth/assoc/deauth trio ate and left no crumbs πŸ”₯ and yes the wowlan family is all here too, we would never forget them.

  • 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)

NAN section is a whole vibe honestly, tiny little neighborhood network, so cute πŸ¦‹

  • 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)
  • 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)

struct cfg80211_ops(9) showing up like the final boss of callbacks πŸ’€ and then struct wiphy(9) at the end of that run, absolutely the main character energy we deserved.


the whole wiphy lifecycle arc: new, register, lock, work, timer-work, unregister, free πŸ’– a full character journey, we stan a consistent narrative.

the "find_*" family is so satisfying honestly, like a little scavenger hunt through the frame πŸ”πŸ’…


regulatory stuff: lowkey intimidating but highkey important, don't sleep on it 🫑

not the leading-double-underscore __cfg80211_get_bss(9) right next to plain cfg80211_get_bss(9) β€” the way that's giving "same energy, different commitment level" 😭 love them both tho.

the connection arc: connect, roam, authorize, disconnect β€” genuinely a whole coming-of-age story πŸŽ€βœ¨

and that's every single one of them, nothing dropped, nothing merged, nothing "fixed" β€” the whole friend group, accounted for πŸ‘‘πŸ’œ

okay so the SEE ALSO section is basically the world's longest group chat and you're getting added to all of it πŸ’– here's the rest of the guest list, no cap, every single one:

like, that's sixty-four cross-references bestie 😭 the nan girlies really showed up, the color/colour-adjacent notify squad ate, and the s1g trio said "we're here too". no skipping, no "etc." β€” every single one is invited to the function, periodt πŸ’…


and that's the whole page, babes πŸŽ€ you just read struct wiph...pe_ext_capab(9) from the Kernel API Manual, source straight out of ./include/net, dated October 2026. go forth and configure things responsibly, love u, bye πŸ‘‘πŸ¦‹

πŸ“¦ where this page comes from