cfg80211_assoc_comeback(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cfg80211_assoc_comeback(9)

okay so picture this: you're deep in the Kernel API Manual (yes bestie, that's the manual name, it's giving ✨official documentation✨), and you stumble onto this little icon. it's called cfg80211_assoc_comeback, and honestly? the name alone is a whole vibe. let's get into it 🫢


🌸 NAME 🌸

cfg80211_assoc_comeback β€” the notification that an association got temporarily rejected with a comeback. like, not a hard no, more of a "not right now, try again later" kind of deal πŸ˜­πŸ’”


✨ SYNOPSIS ✨

void cfg80211_assoc_comeback (struct net_device *netdev , const u8
       *ap_addr , u32 timeout );

that's the whole signature, no cap. one void function, three args, zero drama (okay maybe a little drama, scroll down for the mutex situation πŸ‘€). πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • netdev β€” the network device. literally the main character here, the thing the whole call is about 🌈
  • ap_addr β€” the AP (MLD) address that rejected the association. so like, the address of the one who said "no" πŸ’€ keep the (MLD) in your heart, it's important iykyk
  • timeout β€” the timeout interval value, measured in TUs. that's the "try again in this long" number πŸ•βœ¨

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so the two things you actually need to know before you go call this:

  • this function may sleep. 😴 not a metaphor, not a joke β€” it can literally sleep, so don't be out here calling it from somewhere spicy πŸ”₯
  • the caller must hold the corresponding wdev's mutex. fr fr, that's on you, bestie. this function is not gonna lock it for you. lock it yourself, then call, periodt πŸ’…πŸ‘‘

get those two right and you're slaying. get them wrong and, well… we don't talk about that πŸ™ˆ


πŸ’… SEE ALSO πŸ’…

okay bestie, this is the part where the page hands you the entire extended universe. every single cross-reference, no skips, no "etc." β€” we're doing the full guest list πŸ’–. grab a snack, this one's a scroll.

🌸 where to start

  • Kernel file ./include/net/cfg80211.h Introduction(9) β€” literally the front door, start here
  • Device registration(9) β€” next stop on the tour

πŸ¦‹ channels, rates, bands & the cap collection

this whole cluster is the "what can this radio actually do" squad. ht, vht, he, eht, uhr β€” the glow-up timeline of wifi, all present and accounted for:


πŸ‘‘ actions & configuration (the big one, fr)

  • Actions and configuration(9) β€” this is the main event of this cluster, the rest is the supporting cast
  • struct vif_params(9)
  • struct key_params(9)
  • struct cfg80211_chan_def(9)
  • struct cfg80211_tid_cfg(9)
  • struct cfg80211_tid_config(9)
  • struct cfg80211_fils_aad(9)
  • struct cfg80211_set_hw_timestamp(9)

🌈 chandef besties (channel width obsessed, as they should be)

πŸŽ€ survey, beacon, AP & CSA energy

  • enum survey_info_flags(9)
  • struct survey_info(9)
  • 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)

πŸ’… stations, rates, SAR, mesh & friends

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

πŸ”₯ scanning & BSS list handling

scanning, BSS lists, association requests, connect params, and then it detours straight into wowlan + coalesce because why not. icons only, tbh:

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

🧚 neighbor awareness networking (NAN)

the whole NAN section pops off, it's giving proximity-based main character energy:

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

🫢 auth, PMK, PMSR & mgmt frames

  • 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 cinematic universe

ops, caps, lifecycles, locks, works, hrtimers β€” this is the wiphy lore drop. buckle up:

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

πŸ’œ wiphy allocation & registration

πŸ”’ locking & deferred work (respect the locking, i beg)

πŸŽ€ wireless_dev, our other icon


✨ utility functions

the little helpers that do the actual vibes-to-numbers math:


πŸ“ data path helpers

frame conversion, amsdu checks, element hunting β€” the "make the bytes make sense" crew:


🌈 regulatory enforcement infrastructure

heads up: the regulatory pages are serious business β€” they're about what your radio is legally allowed to do, not just vibes. read them properly, bestie.

πŸ’€ BSS reporting, MLME & assoc notifications


πŸ™ˆ rfkill integration


πŸ¦‹ vendor commands


🧚 test mode


πŸ’– connect / roam / disconnect & all the notifications

the "tell userspace what just happened" hall of fame:

πŸ”₯ cqm & radar & cac & rekey notifications

...and the list literally keeps going, bestie, so buckle up πŸŽ€

Still with me? iconic, ty πŸ’– keep scrolling, we're not done.

okay this is lowkey a whole saga at this point 😭 but every single one stays, no skipping, periodt.

That's the whole list β€” we ate, no crumbs left πŸ’…βœ¨ go read whichever one you actually came for, bestie, iykyk.


And that's a wrap on this page, fr fr πŸ¦‹ it lives in ./include/net, it's dated October 2026, and the page itself is cfg80211_assoc_comeback(9) β€” go forth and associate, you gorgeous nerd πŸŒΈπŸ‘‘

πŸ“¦ where this page comes from