__cfg80211_radar_event(9)

๐Ÿ“ฆ version 7.3.1, in nixpkgs unstable

๐ŸŒˆ NAME ๐ŸŒˆ

okay so bestie, welcome to the Kernel API Manual corner of the group chat ๐Ÿ’… โ€” this page is all about __cfg80211_radar_event, and her whole job description is radar detection event ๐ŸŽฏ๐Ÿ“ก


โœจ SYNOPSIS โœจ

here's the whole vibe, character for character, no cap:

void __cfg80211_radar_event (struct wiphy *wiphy , struct
       cfg80211_chan_def *chandef , bool offchan , gfp_t gfp );

she's a void girlie, so don't go looking for a return value to catch โ€” there isn't one ๐Ÿซถ


๐ŸŽ€ ARGUMENTS ๐ŸŽ€

four besties walk into a function, and here's the tea on each of them:

  • wiphy โ€” the wiphy. that's it, that's her whole thing ๐Ÿ’€ literally just the wiphy.
  • chandef โ€” the chandef for the current channel ๐ŸŒธ
  • offchan โ€” the radar has been detected on the offchannel chain ๐Ÿ‘€ so if this is set, the detection happened over there, not on the channel you're sitting on.
  • gfp โ€” context flags โš™๏ธ

๐Ÿ”ฅ DESCRIPTION ๐Ÿ”ฅ

okay so here's the moment: this function is called when a radar is detected on the current chanenl ๐Ÿ“กโœจ

yes, "chanenl" โ€” that's the original's spelling and we're keeping it verbatim, she's iconic, we stan a typo ๐Ÿ™ˆ๐Ÿ’–

so like, radar shows up on the channel you're currently on โ†’ this is the function that gets called. that's the whole scenario, and it's giving main character energy ๐ŸŒŸ


more parts coming, bestie โ€” don't go anywhere ๐Ÿ’œ๐Ÿฆ‹

๐Ÿฆ‹ SEE ALSO ๐Ÿฆ‹

Okay bestie, this is the extended friend group ๐Ÿ’– โ€” every single thing below is a real doc living in this same (9) manual, so if you're lost, literally just pick one and go. Starting with the kernel file itself:

  • Kernel file ./include/net/cfg80211.h

Then the big-picture intros, because you gotta start somewhere:


๐ŸŒธ the ieee80211 channel / band / cap fam

This whole chunk is the main character lineup of channel flags, rate flags, and capability structs โ€” no cap, you'll see these names everywhere:

  • 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)
  • struct ieee80211_he_obss_pd(9)
  • struct cfg80211_he_bss_color(9)
  • struct ieee80211_sta_ht_cap(9)
  • struct ieee80211_sta_vht_cap(9)
  • struct ieee80211_sta_he_cap(9)
  • struct ieee80211_eht_mcs_nss_supp(9)
  • struct ieee80211_sta_eht_cap(9)
  • struct ieee80211_sta_uhr_cap(9)
  • struct ieee80211_sband_iftype_data(9)
  • enum ieee80211_edmg_bw_config(9)
  • struct ieee80211_edmg(9)
  • struct ieee80211_sta_s1g_cap(9)
  • struct ieee80211_supported_band(9)

And the sband helper squad ๐Ÿซถ โ€” note that _ieee80211_set_sband_iftype_data(9) has the underscore, it's a whole different vibe from the one without it:


โœจ Actions and configuration โœจ

Actions and configuration(9) โ€” this is the section where the actual doing stuff lives, and it pulls in a LOT of friends:

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

Then the channel-definition function clique (they all talk about chandefs, obviously, iykyk):

Survey + crypto + beacon-ish stuff, aka the BSS housekeeping crew ๐Ÿงน:

  • 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!! ๐Ÿ‘‘ The station-parameter and rate-info family, plus all the stats you could ever want:

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

SAR stuff (the power-limit girlies) and a couple of getters:

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

Monitor / mesh path / bss-param corner of the section ๐Ÿ’€:

  • 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 and BSS list handling ๐Ÿฆ‹

Scanning and BSS list handling(9) โ€” yes, scanning gets its own whole doc, and the scan structs are so organized:

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

Then the connect/auth/assoc pipeline โ€” auth request, allll the assoc friends, then deauth and disassoc (the sad ones) ๐Ÿ˜ญ:

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

Power-save / wowlan / coalesce gang ๐ŸŒˆ (they show up together, always):

  • 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) ๐Ÿงš

Neighbor Awareness Networking (NAN)(9) โ€” the NAN crew, all together, all matching ๐ŸŒธ:

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

Then a lil mixed bag โ€” pmk, external auth, FTM responder stats, and the whole PMSR result/request set ๐ŸŽ€:

  • 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 era ๐Ÿ’œ

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

The wiphy lifecycle + priv accessors + the work-queue helpers (there are so many of these, and honestly? iconic that each one gets a doc) โœจ:

And the wireless-dev side of the family ๐Ÿซถ:


โญ Utility functions โญ

Utility functions(9) โ€” channel math, rate math, and header-length math. Numbers go brrr ๐Ÿ”ฅ:


๐Ÿ’€ Data path helpers ๐Ÿ’€

Data path helpers(9) โ€” packet translation + element hunting. _exthdr and plain are two separate docs, don't @ me:

The _match / _elem / _ie / _ext_ / _vendor_ finder squad โ€” yes, every combo has its own doc, and that's on periodt:


๐ŸŒˆ Regulatory enforcement infrastructure ๐ŸŒˆ

Regulatory enforcement infrastructure(9) โ€” the rules girlies ๐ŸŽ€:

Internal regulatory db functions(9) โ€” the internal one, aka the backstage pass:


๐Ÿ“ scanning + BSS notifications & mgmt (the long tail) ๐Ÿ“

Deep breath bestie, this is a big run of function docs, all siblings:


๐Ÿ”ฅ RFkill integration ๐Ÿ”ฅ

RFkill integration(9):


๐Ÿ‘‘ Vendor commands ๐Ÿ‘‘

Vendor commands(9) โ€” reply skbs, sender lookup, and the three event alloc flavors (plain, _ucast, and the one that just fires the event):

๐Ÿ™ˆ Test mode ๐Ÿ™ˆ

Test mode(9) โ€” same shape as the vendor crew, but for testmode:


๐Ÿงš connect / roam / disconnect notifiers ๐Ÿงš

Station bookkeeping + the tid-stats allocators (there's a link-flavored one too, don't skip it):


๐Ÿ’– mgmt rx/tx, control port, and all the notify friends ๐Ÿ’–

And that's the whole guest list for this section ๐Ÿ’… โ€” more coming up next, so don't go anywhere.

okay continuing the list, bestie โ€” do not scroll past these, they're literally the whole friend group ๐Ÿ‘‡


and that's the whole list, no skips, no cuts, we ate and left zero crumbs ๐Ÿ“๐Ÿ’–

this lil page lives in ./include/net and it's the October 2026 edition โ€” go be iconic with it, ily, bye ๐ŸŽ€โœจ๐Ÿ’…

๐Ÿ“ฆ where this page comes from