cfg80211_connect_result(9)

📦 version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so <pink>cfg80211_connect_result</pink> — it's the function that tells cfg80211 how the connection went. like, the whole notify-cfg80211-of-connection-result situation. from the Kernel API Manual, bestie, section 9. 💅

🌸 SYNOPSIS 🌸

void cfg80211_connect_result (struct net_device *dev , const u8 *bssid ,
const u8 *req_ie , size_t req_ie_len , const u8 *resp_ie , size_t
resp_ie_len , u16 status , gfp_t gfp );

no cap, that's the whole signature — copy it exactly or it's not gonna compile, iykyk 🫶

🎀 ARGUMENTS 🎀

  • dev — the network device, bestie. your net_device. that's the one. 💖
  • bssid — the BSSID of the AP you connected to ✨
  • req_ie — the association request IEs (it may be NULL, ok? like it's allowed to be a whole nothing-burger)
  • req_ie_len — the length of those association request IEs 🌸
  • resp_ie — the association response IEs (also may be NULL, same energy)
  • resp_ie_len — length of the assoc response IEs, slay 🦋
  • status — the status code, and listen: use WLAN_STATUS_SUCCESS for a successful connection. and if your device literally cannot give you the real status code for failures? use WLAN_STATUS_UNSPECIFIED_FAILURE. that's the move 🙈
  • gfp — allocation flags ⭐

💜 DESCRIPTION 💜

okay so here's the vibe check: your underlying driver should call this once execution of the connection request from connect has been completed. like, connect said go, the thing happened, now you're reporting back. main character energy. 👑

this one is similar to cfg80211_connect_bss, except that cfg80211_connect_bss lets you specify the exact bss entry. so like, cousins. same family, slightly different flex. 🧚

⚠️ and this is the important bit, so read it twice bestie — only one of these functions should be called: cfg80211_connect_bss, cfg80211_connect_result, cfg80211_connect_timeout, or cfg80211_connect_done. not two. not "well maybe just this once." one. periodt. 💀

to be continued… 🌈

🔗 SEE ALSO 🔗

okay bestie, buckle up, because this is the section. this is the whole extended universe of cfg80211, like the group chat of every struct and function that's even tangentially in this family 💖 ngl the original just dumps all of them in a wall of text, so i'm giving you the same names but sorted into little vibe clusters so your brain doesn't evaporate. every single one is here, no cap, nothing skipped 🫶

🌱 the starting point

  • ./include/net/cfg80211.h Introduction(9) — the kernel file this whole page lives in, and the intro page, iykyk
  • Device registration(9)

📡 channels, rates & the basics of a BSS

  • enum ieee80211_channel_flags(9), struct ieee80211_channel(9), enum ieee80211_rate_flags(9), enum ieee80211_bss_type(9), enum ieee80211_privacy(9), struct ieee80211_rate(9)

🦋 all the capability structs (ht / vht / he / eht / uhr, we love an acronym)

⚙️ Actions and configuration (aka the big one)

🔍 Scanning and BSS list handling

  • 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)
  • auth/assoc/connect: 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) — yes, that cfg80211_connect_params, the one this whole page is literally about 💅
  • wiphy params + pmksa + wowlan: 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)
  • gtk rekey / ft ies / mgmt tx / qos: 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)

  • 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-adjacent & measurement things

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

🧰 Utility functions

🚀 Data path helpers

📜 Regulatory enforcement infrastructure

📣 scan done, BSS informing & MLME event notifications

this cluster is giving "the driver calls back into cfg80211 and the whole thing lights up" 💫

📴 RFkill integration

🛍️ Vendor commands

🧪 Test mode

🏁 connection, roaming, station & mgmt-tx callbacks (the grand finale)

ok that's the whole list, fr fr — nothing dropped, nothing merged, every single (9) reference is accounted for 🎀

okay bestie the SEE ALSO list is still going — she's long, she's thorough, and honestly she ate 💅 we're in the home stretch now, so here's everyone else getting a shoutout, in order, no skips (fr fr, i counted) 🎀

the beacon / reg girlies — yes they all start with cfg80211_reg, iconic of them ✨

channel switch committee 🦋

the conversion girlies (operating class ⇄ band ⇄ chandef ⇄ khz, the whole glow-up pipeline) 🌈

the one-off icons 💫

the combinations / link management crew (busy, booked, and thriving) 👑

ext feature duo 🌸

NAN squad, part one — lowkey the most mysterious friend group in the doc set 🫶

auth / measurement / assorted main characters ⭐

the colour change committee — genuinely obsessed with this whole arc, no notes 🎨

6 GHz + MLO + channels crew 🔥

NAN squad, part two — the sequel 🧚

debugfs besties (locked and loaded, literally) 🔒

S1G trio 💜

and the final one, closing us out 🌟

okay and that's the whole list, bestie — 64 cross-references, all present and accounted for, not a single one left behind 😭✨ go click around, that's what SEE ALSO is for, iykyk.

real talk: these are just pointers to other pages in the same set, so if one of them looks like your fave, go read it instead of guessing 💅

and that's the page!! 🎀 it lives in ./include/net, it's dated October 2026, and it's the man page for cfg80211_connect_result(9) — go off, bestie, you understood the whole thing 🫶💖

📦 where this page comes from