cfg80211_reg...ck_beaconing(9)

📦 version 7.3.1, in nixpkgs unstable

okay so this is the cfg80211_reg...ck_beaconing(9) page from the Kernel API Manual, and we’re doing part 1 💅✨

🎀 NAME 🎀

cfg80211_reg_check_beaconing — check if beaconing is allowed 👑

✨ SYNOPSIS ✨

the function signature is literally this, bestie:

bool cfg80211_reg_check_beaconing (struct wiphy *wiphy , struct
       cfg80211_chan_def *chandef , struct cfg80211_beaconing_check_config *cfg
       );

🌸 ARGUMENTS 🌸

  • wiphy — the wiphy 👑
  • chandef — the channel definition 🦋
  • cfg — additional parameters for the checking 🎀

💖 RETURN 💖

returns true if there is no secondary channel or the secondary channel(s) can be used for beaconing (i.e. is not a radar channel etc.) ✨📡

it’s giving “beaconing allowed?” and the return type is bool, periodt 💅

✨ SEE ALSO ✨

okay so this is the whole extended friend group 💖 — literally every page down here is its own (9) manpage, so if you're bored after this one you have options. Starting with the file they all live in:

Kernel file ./include/net/cfg80211.h

next chunk is the config-and-actions era, which is lowkey where all the drama happens 💅

scanning squad, rise 🦋

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

NAN girlies, this is your moment ✨

utility functions, the reliable besties 🫶

data path helpers, aka the ones doing cardio 🏃‍♀️

regulatory enforcement infrastructure — the actual rule-followers 💀

RFkill integration 🔥

vendor commands, because everybody wants their own ✨

test mode, respectfully 💅

and bestie we are literally not done yet — the rest of the crew is right in the next chunk 🫶

okay so the SEE ALSO list keeps going and honestly it's giving group chat with 64 members and everyone is typing 😭💀 but bestie we are NOT leaving anyone on read. Full roster, in order, every single one:

the beacon & regulatory crew 🦋

the operating-class / chandef girlies 📡

the interface & netdevice main characters 💅

the IE-splitting icons ✨

wowlan / crit-proto / channels 🌸

combinations & radio indexing (the math girlies) 🧮

stopping things (respectfully) 🛑

feature flags 🚩

the NAN girlies (they have a whole saga) 🫧

auth, PMSR & assoc 🔐

BSS + colour change (aesthetic era) 🌈

6 GHz & MLO (the new gen) 👑

more NAN, because of course 💜

debugfs (handle with care, bestie) 🔍

S1G things 🍓

and last but never least ⭐

periodt, that's the whole crew, nobody skipped 💖 ngl if you actually read all 64 of those you have my full respect, go drink some water 🫶

lowkey a moment of appreciation for whoever maintains this list btw — the way it just keeps going and every single entry is still there? iconic. no cap.

okay and finally the lil' fine print, but make it cute: this whole thing lives over in ./include/net, and the date on it is October 2026 — so yes, it's a certified October 2026 baddie, documented and everything ✨💅 love that for us. mwah, go forth and configure your beacons responsibly 🎀

📦 where this page comes from