REGULATORY ENFORCEMENT INFRASTRUCTURE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ Regulatory Enforcement Infrastructure πŸŽ€

ok so bestie, we're in the Kernel API Manual, section 9 β€” yes, the big one, the kernel-flavored one β€” and this page is genuinely the shortest glow-up you'll ever see. πŸ’…

The entire body of this page, the whole thing, is literally:

TODO

That's it. That's the page. 🫢 No synopsis, no options, no environment variables, no exit statuses, no SEE ALSO β€” nothing to memorise, nothing to break, no cap. The lights are on and the docs are, uh, not home yet. 😭

Fair warning: because the content is just TODO, there's nothing here yet to tell you how regulatory enforcement infrastructure actually behaves. Don't go guessing at flags or behaviour from this one β€” the real details live in whatever fills this in later. πŸ™ˆ

Stay tuned, bestie β€” this is part 1 of 3, so the rest is coming. ✨

✨ SEE ALSO ✨

Okay bestie, this is the part where the manpage dumps literally everyone it knows on you at once, like a group chat with 400 members and you're supposed to remember all their names πŸ’€. Deep breaths. It's a lot, but it's all right here, and ngl some of these are lowkey iconic.

First up, there's a whole kernel file doing main character energy: ./include/net/cfg80211.h, and then the general intro-and-registration crew:

Then the channel/rate/bss/privacy core, i.e. the fundamentals:

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

The HE / EHT / UHR capability girlies (they're booked and busy):

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

Band/iftype data and the EDMG + S1G corner of the universe:

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

The setter/getter helper besties for sband iftype data (and yes, _ieee80211_set_sband_iftype_data has a leading underscore, don't come for me):

And one lone frequency-limits reader:


Okay next block is Actions and configuration, and it is long. Like, "we're gonna be here a while" long. Slay for completeness though πŸ’….

The starter pack of params and definitions:

  • Actions and configuration(9)
  • 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 chandef girlies β€” get into it:

DFS content, because radar is not a vibe to ignore:

The primary/NPCA/DBE + width + power + S1G pri-width situation:

Survey and crypto settings (the "what's the channel doing" girlies):

  • enum survey_info_flags(9)
  • struct survey_info(9)
  • struct cfg80211_crypto_settings(9)

The MBSSID / RNR / beacon / ACL / FILS / probe-resp / S1G short beacon family β€” literally all here:

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

AP settings and updates, CSA and colour-change settings, plus iface combination params:

  • 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-land: apply masks, txpower, link station params, TTLM, station params, del params, station type, and the check-station-change function:

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

Rate info and BSS params (iconic little duo):

  • enum rate_info_flags(9)
  • enum rate_info_bw(9)
  • struct rate_info(9)
  • enum bss_param_flags(9)
  • struct sta_bss_parameters(9)

TXQ / TID / link station / station info (the stats besties):

  • struct cfg80211_txq_stats(9)
  • struct cfg80211_tid_stats(9)
  • struct link_station_info(9)
  • struct station_info(9)

SAR stuff, because specific absorption rate is a whole thing:

  • struct cfg80211_sar_sub_specs(9)
  • struct cfg80211_sar_specs(9)
  • struct cfg80211_sar_freq_ranges(9)
  • struct cfg80211_sar_capa(9)

Get-station, monitor flags, mesh path info, wiphy bss params, bss params, mesh config/setup, OCB setup, and txq params:

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

Next up, Scanning and BSS list handling, aka the "where are the networks at" section of the group chat:

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

The BSS element/IE getters (twins, basically):

Auth / assoc / ML reconf / deauth / disassoc β€” the connection-drama lineup:

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

IBSS params, BSS selection, connect params, connect-params-changed, wiphy params flags, PMKSA:

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

Packet patterns and WoWLAN everything (TCP, wowlan, coalesce rules, coalesce, ND match, ND info, wakeup):

  • 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 update, mgmt tx params, DSCP exception/range, and QOS map:

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

Then Neighbor Awareness Networking (NAN) β€” she has her own whole friend group, respectfully:

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

PMK conf, external auth, FTM responder stats, and the PMSR result/request crew:

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

Okay and then we get to the big structural girlies: mgmt frame regs, cfg80211 ops, wiphy flags, iface limits/combinations, wowlan support, coalesce support, vendor command flags, opmode flags, sta opmode info, vendor command, iftype ext capab, get-iftype-ext-capa, PMSR capabilities, iftype AKM suites, and the radio config/freq-range/radio trio:

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

NAN flags/capa, then struct wiphy(9) herself (yes she gets her own entry, queen πŸ‘‘):

  • enum wiphy_nan_flags(9)
  • struct wiphy_nan_capa(9)
  • struct wiphy(9)

The wiphy lifecycle + access + work helpers, all of them, no skips:

Work queue / cancel / flush, regular and delayed:

And the hrtimer work versions, because apparently one work family wasn't enough:

AP reg power, wireless dev, and the wdev accessors:


Utility functions, aka the little helpers that fix everything behind the scenes:

Radiotap iterator, header length getters, and mesh header length β€” the "how long is this actually" girlies:


Data path helpers β€” the ones that actually move the packets, no cap:

Element/IE finding functions, matching and plain, ext and vendor included:

RNR iteration and defrag, plus the layer-2 update sender:

Regulatory hinting, custom regd, freq reg info, initiator name, and pre-CAC:

Internal regulatory db functions (yes, "internal", don't @ me):


Then the scan-done + sched-scan results/stopped trio (plus the _locked version, which is its own thing):

BSS frame data, new BSSID generation, element inheritance, profile merge, frame type, IEs channel number, and SSID equality:

BSS informing + getting + ref/put/unlink/iter (the double-underscore variant is right there too):

MLME mgmt rx/tx, auth timeout, assoc resp data, rx assoc resp, assoc failure + its struct, unprot mgmt rx, Michael MIC failure, IBSS joined, and the new-peer-candidate notify:


RFkill integration β€” three functions, very demure:


Vendor commands β€” the "compliant with your favorite chipset" corner:


Test mode β€” yes it's a whole section:

FILS resp params, connect resp params, connect done/bss/result/timeout, roam info, roamed, port authorized, and disconnected:

Ready-on-channel, remain-on-channel expired, tx mgmt expired, sinfo TID stats alloc (both variants), sinfo release content, new sta, del sta sinfo, del sta, conn failed:

RX info, rx mgmt (ext + khz + plain), tx status (the struct + ext + plain), control port tx status, and rx control port:

CQM notifications (rssi, pktloss, txe, beacon loss), radar event, sta opmode change notify, CAC event, background CAC abort, GTK rekey notify, PMKSA candidate notify:

Spurious frame, unexpected 4addr frame, probe status, and the OBSS beacon reporters (khz + plain), and last but not least the beaconing check config:

okay so the SEE ALSO list continues and it is long β€” I refuse to make you read a wall of text, so I've grouped the whole thing into lil clusters πŸŽ€ every single reference is here, nothing skipped, and yes they're all (9) pages. let's go ✨

πŸ’… beaconing & channel switches

πŸ¦‹ operating class & chandef math

πŸ“ tdls & bitrate

✨ netdevice registration era

🧚 fast transition, p2p & IE splitting

🌸 wowlan, critical proto & channel counting

πŸ‘‘ combinations

πŸ’€ stopping things (dramatic)

⭐ extended features

πŸŽ€ NAN, part one

🌈 auth, PMSR & iftype

πŸ¦‹ bss & colour change

πŸ’œ MLO & channel checks

🫢 NAN, part two (she's back)

πŸ”₯ debugfs, S1G & incumbent signal


aaaand that's the whole cross-reference list, every single one accounted for πŸ’– fr fr that was 64 of them.

little sign-off moment bc the footer deserves love too: this page lives at ./include/net, comes from the Kernel API Manual, and it's dated October 2026 πŸŽ€βœ¨ go forth and regulate, bestie πŸ‘‘

πŸ“¦ where this page comes from