cfg80211_re...beacon_relax(9)

๐Ÿ“ฆ version 7.3.1, in nixpkgs unstable

๐ŸŒธ NAME ๐ŸŒธ

okay so we're deep in the Kernel API Manual rn, and the main character is cfg80211_reg_can_beacon_relax โ€” she checks if beaconing is allowed with relaxation. Yes bestie, "with relaxation" is literally carrying the whole vibe: this is the more chill, more permissive check. ๐Ÿ’…โœจ

โœจ SYNOPSIS โœจ

bool cfg80211_reg_can_beacon_relax (struct wiphy *wiphy , struct
cfg80211_chan_def *chandef , enum nl80211_iftype iftype );

๐Ÿ’… ARGUMENTS ๐Ÿ’…

  • wiphy โ€” the wiphy. That's the argument, that's the whole assignment. The wiphy struct is pulling up to the function, no cap. ๐Ÿซถ
  • chandef โ€” the channel definition. It's the cfg80211_chan_def situation telling us what channel setup we're looking at. ๐ŸŒˆ
  • iftype โ€” the interface type, aka the enum nl80211_iftype value. She's here to say what kind of interface we're working with. ๐Ÿ‘‘

๐Ÿ”ฅ RETURN ๐Ÿ”ฅ

Returns true if there is no secondary channel or if the secondary channel(s) can be used for beaconing โ€” i.e. it's not a radar channel etc. ๐Ÿšจโœจ

This version also checks if IR-relaxation conditions apply, so beaconing is allowed under more permissive conditions. It's giving "we checked the vibe and relaxed the rules a lil bit" and honestly? Iconic. ๐Ÿ’–

๐Ÿซถ CONTEXT ๐Ÿซถ

Requires the wiphy mutex to be held.

Translation for the besties: hold the wiphy mutex before you call this. No mutex, no beaconing check โ€” it's giving "read the room" but make it kernel locking. ๐Ÿ˜ญ๐Ÿ”’๐Ÿ’€

๐ŸŽ€ SEE ALSO ๐ŸŽ€

Okay bestie, real talk: this SEE ALSO section is not a vibe check, it's a whole rolodex ๐Ÿ˜ญ. Every single one of these is a section (9) man page and they all basically live in ./include/net/cfg80211.h unless the entry literally spells out a path. Strap in, we're going shopping ๐Ÿ›๏ธโœจ

๐ŸŒธ the origin story

  • Kernel file ./include/net/cfg80211.h โ€” the actual header file this whole page is describing, the mothership, the source of truth ๐Ÿ’–
  • Introduction(9)
  • Device registration(9)

๐Ÿฆ‹ bands, channels, rates & caps (the capability girlies)

Channel flags, rate flags, BSS types, privacy โ€” plus every HT/VHT/HE/EHT/UHR capability struct you could ever want, and the S1G + EDMG crowd too. It's giving acronym soup but make it fashion ๐Ÿ’…


๐Ÿงš actions and configuration

The main character section ngl โ€” if you're configuring anything, you're gonna be living in these ๐Ÿซถ

  • Actions and configuration(9)
  • struct vif_params(9)
  • struct key_params(9)

โญ chandef supremacy

The way these all just say chandef over and over โ€” iconic, honestly. Width, validity, DFS, NPCA, DBE, primary channel, all of it ๐Ÿ”ฅ

๐ŸŽ€ survey + AP setup energy

Beacons, ACLs, MBSSID, RNR, FILS discovery, unsolicited broadcast probe responses, CSA, colour change โ€” the full AP glow-up kit ๐Ÿ’–

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

๐ŸŒˆ station era

Stations, links, TTLM, rates, txq stats, station info, SAR specs โ€” yes there are four SAR entries, they really said collect them all ๐Ÿ“

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

๐Ÿฆ‹ mesh, OCB & the rest of the config crew

  • 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

Scan requests, scheduled scans, match sets, the BSS cache, and then a whole journey through auth/assoc/deauth/disassoc/IBSS/connect params โ€” plus WoWLAN, coalesce, GTK rekey, QoS maps, and NAN ๐Ÿซถ

  • 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, PMK & measurement besties

Neighbor Awareness Networking entries, external auth, FTM responder stats, and the whole PMSR request/result pipeline โ€” plus OWE and management frame regs ๐Ÿ’…

  • 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)
  • 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 section (a whole personality)

This is the big one, bestie โ€” wiphy flags, iface combos, WoWLAN support, vendor commands, opmode, radio config, NAN capa, and then so many wiphy lifecycle helpers. Lock it, unlock it, queue work on it, cancel work on it โ€” we do it all ๐Ÿ’€โœจ


๐ŸŽ€ utility functions

Little helpers that carry the whole operation โ€” channel โ†” frequency conversions, PSC checks, radio range validation, response rates, radiotap iteration, and header length math ๐Ÿงฎ๐Ÿ’–


๐Ÿซถ data path helpers + element hunting

802.3 conversion, AMSDU checks, tunnel proto, mesh header stripping, 802.1d classification โ€” and then the find the IE squad, RNR iteration, defragmentation, and layer 2 updates ๐Ÿ”ฅ


๐ŸŒˆ regulatory enforcement infrastructure

Regulatory hints, custom regd application, frequency reg info, initiator names, pre-CAC gating โ€” plus the internal regdb query ๐Ÿ’œ


โญ reporting, BSS bookkeeping & MLME notifications

Scan done, sched scan results/stopped, informing BSS frames, BSS merging, get/ref/put/unlink, and then every MLME upcall you could possibly need ๐Ÿ˜ญ


๐Ÿฆ‹ RFkill, vendor commands & test mode

Hardware rfkill state (with a reason, fancy), polling start/stop, then the vendor reply/event allocation crew, then test mode's reply/event helpers ๐Ÿ™ˆ


๐Ÿ’… connection lifecycle notifications

FILS resp params, connect resp params, connect done/bss/result/timeout, roaming info, port authorization, disconnection, remain-on-channel, TX mgmt expiry, and station info tid-stats allocation ๐Ÿซถ


โœจ management TX/RX, control port & the notify squad

Rx info, mgmt rx variants, tx status variants, control port, CQM notifications for RSSI/pktloss/txe/beacon loss, radar + CAC events, gtk rekey, PMKSA candidates, spurious frames, probe status, and OBSS beacon reporting ๐Ÿ’€๐Ÿ”ฅ

โ€ฆand the list just keeps going, bestie. No seriously, it does. Here's the rest of the squad, in order, no skips ๐Ÿ’…






ok that's the whole cross-reference crowd, no cap, not one of them skipped. go click through, iykyk ๐Ÿ’…

And that's the page, bestie โ€” we made it to the end, which deserves a little moment ๐ŸŽ€ This one came out of the tree at ./include/net, it's dated October 2026, and the whole thing lives under the name of cfg80211_re...beacon_relax(9). Slay, go read the code, ily ๐Ÿฆ‹๐Ÿ’œ

๐Ÿ“ฆ where this page comes from