cfg80211_cq..._loss_notify(9)

📦 version 7.3.1, in nixpkgs unstable

💖 cfg80211_cqm_beacon_loss_notify(9) 💖

okay so bestie, welcome to the Kernel API Manual, and specifically to cfg80211_cqm_beacon_loss_notify — yes the header up top got chopped to cfg80211_cq..._loss_notify(9) because apparently even manpage headers have a character limit and honestly? relatable. anyway. it's the beacon-loss-notify girlie and she's here to spill. 🫶

✨ NAME ✨

cfg80211_cqm_beacon_loss_notify — it's giving beacon loss event, no cap 💀

🌸 SYNOPSIS 🌸

void cfg80211_cqm_beacon_loss_notify(struct net_device *dev, gfp_t gfp);

like, that's the whole signature. void return, two args, she's neat, she's tidy, she's iconic ✨

🎀 ARGUMENTS 🎀

  • dev — the network device, aka the struct net_device * in question. your main character. 👑
  • gfp — the context flags (gfp_t), iykyk. lowkey tells the kernel what kind of allocation context we're in. 🌈

🦋 DESCRIPTION 🦋

so what does she do? literally just: notify userspace about beacon loss from the connected AP. that's it. that's the whole vibe. 📡💔

like, the connected access point stopped sending beacons, and this function is the messenger that lets userspace know about it. no cap, that's the entire job. she doesn't fix it, she doesn't reconnect you, she just tells — and honestly? communication queen. 💅✨

fr fr this is the "hey bestie something's wrong" text of the wireless stack. 🫶

to be continued… more parts incoming, don't go anywhere 🧚💜

Back at it, bestie 💖 so after the whole DESCRIPTION moment, the page gives you the full SEE ALSO squad — and babes, it is long. Like, every single cross-reference in the cfg80211 cinematic universe is listed here, and I'm gonna walk you through all of them. No skipping, no "etc." — we don't do that here ✨

Everything kicks off with the home base:

  • Kernel file ./include/net/cfg80211.h Introduction(9)
  • Device registration(9)

🦋 the channel / rate / capability core

These are the foundational vibes — channels, rates, and every capability struct you'll ever touch:

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

Then the HE / EHT / UHR era stuff — yes king, we're in the modern-Wi-Fi section now 👑

  • 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 helper fam that pokes at all of the above — some of these are lowkey internal, so mind the underscores:

🎀 Actions and configuration(9)

This is the big one, and it starts with Actions and configuration(9) — honestly the whole do-stuff-and-configure-things wing of the library. First up, the setup structs:

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

💅 the chandef clique

If it has "chandef" in the name, it's here. All of it. Get comfy:

Then survey + crypto + the multi-BSSID / RNR / beacon cluster 🎀:

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

🌸 station stuff (the whole roster)

Interface combos, station params, and the entire station-info ecosystem:

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

🫶 SAR + mesh + the rest of the config crew

  • 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 and BSS list handling(9)

Scanning bestie era — Scanning and BSS list handling(9) opens the door and then it's just so many structs:

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

Then power-save-ish + WoWLAN + coalesce energy (the sleepy-time arc 😴):

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

NAN hive, rise 🐝 — Neighbor Awareness Networking (NAN)(9) brings its whole clique:

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

Followed by security/auth + ranging (PMK, external auth, FTM, PMSR) 🔥:

  • 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 cfg80211_ops + wiphy industrial complex

This is the main-character section, no cap. struct cfg80211_ops(9) is the driver-facing ops table, and it hangs with the whole wiphy family:

  • 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 lifetime + locking + workqueue squad

Create it, register it, lock it, queue work on it, free it. The full lifecycle glow-up:

🦋 wireless_dev (wdev) besties

🌈 Utility functions(9)

The little helpers that just work: Utility functions(9) ✨

💜 Data path helpers(9)

Where the packets actually get massaged — Data path helpers(9) plus the element-finding and element-defrag crew:

🎀 Regulatory enforcement infrastructure(9)

Legal-radio-hours squad 📻 — Regulatory enforcement infrastructure(9):

🍓 Internal regulatory db functions(9)

🌸 scan / BSS notification long tail

Deep breath bestie, this is the notification era — every "hey something happened" callback in the book:

🫶 RFkill integration(9)

💅 Vendor commands(9)

Because every vendor wants their own special lil commands:

🔥 Test mode(9)

👑 connect / roam / port-auth notifications

The connection-lifecycle icons, staying iconic:

🦋 TID stats + station notifications

🌈 mgmt / control-port / rx-tx status fam

🎀 CQM + radar + CAC + rekey + PMKSA notifications

⭐ weird-frame + probe + OBSS + beaconing check (final stretch of this part)

And that's the whole SEE ALSO reference dump for this chunk, bestie — every single one, accounted for, not a crumb left behind 💖 keep scrolling, 'cause there's more coming and we're not done yet ✨

...and the list keeps going, bestie — we're so not done yet 😤💅 these are all the sibling pages that live in the same corner of the kernel, and yes, every single one of them is getting its moment:

That's the whole friend group, bestie — sixty-three icons and not one of them skipped 🫶✨ go click through man 9 on any of them whenever the curiosity hits, they're all right there waiting for you.

and that's a wrap on the whole page! this one comes straight out of ./include/net, dated October 2026, and it's the cfg80211_cq..._loss_notify(9) girlies' very own page. thanks for reading all three parts, ily, bye 💖🎀🦋
📦 where this page comes from