STRUCT CFG80211_PMSR_FTM_REQUEST_PEER(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

okay bestie, this is the struct cfg80211_pmsr_ftm_request_peer(9) page from the Kernel API Manual, and no cap: it's the FTM request data struct. Short name, big main-character energy. 🩷

✨ SYNOPSIS ✨

here's the actual struct, bestie — every field exactly where it lives, copy-paste clean:

       struct cfg80211_pmsr_ftm_request_peer {
           enum nl80211_preamble preamble;
           u16 burst_period;
           u8 requested:1, asap:1, request_lci:1, request_civicloc:1,
       trigger_based:1, non_trigger_based:1, lmr_feedback:1, rsta:1;
           u8 num_bursts_exp;
           u8 burst_duration;
           u8 ftms_per_burst;
           u8 ftmr_retries;
           u8 bss_color;
           u32 request_type;
           u32 min_time_between_measurements;
           u32 max_time_between_measurements;
           u8 availability_window;
           u32 nominal_time;
           u32 num_measurements;
           u64 ingress_distance;
           u64 egress_distance;
           u8 pd_suppress_range_results:1;
        };

🫶 Members 🫶

  • preamble — frame preamble to use. it's giving “how should this frame start?” energy ✨
  • burst_period — burst period to use. 🎀
  • requested — indicates FTM is requested. 📨
  • asap — indicates to use ASAP mode. ⚡
  • request_lci — request LCI information. 🗺️
  • request_civicloc — request civic location information. 🏙️
  • trigger_based — use trigger based ranging for the measurement. If neither trigger_based nor non_trigger_based is set, EDCA based ranging will be used. 👀
  • non_trigger_based — use non trigger based ranging for the measurement. If neither trigger_based nor non_trigger_based is set, EDCA based ranging will be used. 👀
  • lmr_feedback — negotiate for I2R LMR feedback. Only valid if either trigger_based or non_trigger_based is set. 🔁
  • rsta — Operate as the RSTA in the measurement. Only valid if lmr_feedback and either trigger_based or non_trigger_based is set. 👑
  • num_bursts_exp — number of bursts exponent. math girlies rise 🧮
  • burst_duration — burst duration. If trigger_based or non_trigger_based is set, this is the burst duration in milliseconds, and zero means the device should pick an appropriate value based on ftms_per_burst. ⏱️
  • ftms_per_burst — number of FTMs per burst. If set to 0, the firmware or driver can automatically select an appropriate value. 🫶
  • ftmr_retries — number of retries for FTM request. 🔂
  • bss_color — the bss color of the responder. Optional. Set to zero to indicate the driver should set the BSS color. Only valid if non_trigger_based or trigger_based is set. 🎨
  • request_type — ranging request type, one of enum nl80211_peer_measurement_ftm_req_type. Defaults to NL80211_PMSR_FTM_REQ_TYPE_INFRA if not specified. 🏷️
  • min_time_between_measurements — minimum time between two consecutive range measurements in units of 100 microseconds, for non-trigger based ranging. Should be set as short as possible to minimize turnaround time, since two-way ranging with delayed LMR requires two measurements. Only valid if non_trigger_based is set. ⏳
  • max_time_between_measurements — maximum time between two consecutive range measurements in units of 10 milliseconds, for non-trigger based ranging. Acts as a session timeout; if exceeded, the ranging session should be terminated. Only valid if non_trigger_based is set. ⌛
  • availability_window — duration of the availability window (AW) in units of 1 millisecond (0-255 ms). Only valid if non_trigger_based is set. If set to 0, the firmware or driver can automatically select an appropriate value. 🪟
  • nominal_time — Nominal duration between adjacent availability windows in units of milli seconds. Only valid if non_trigger_based is set. If set to 0, the firmware or driver can automatically select an appropriate value. 🕰️
  • num_measurements — number of Availability Windows (AWs) to schedule for non-trigger-based ranging. Each AW may contain multiple FTM exchanges as configured by ftms_per_burst. Only valid if non_trigger_based is set. If set to 0, the firmware or driver can automatically select an appropriate value. 📊
  • ingress_distance — optional ingress threshold in units of mm. When set, the measurement result of the peer needs to be indicated if the device moves into this range. Measurement results need to be sent on a burst index basis in this case. 🚪
  • egress_distance — optional egress threshold in units of mm. When set, the measurement result of the peer needs to be indicated if the device moves out of this range. Measurement results need to be sent on a burst index basis in this case. If neither or only one of ingress_distance and egress_distance is set, only the specified threshold is used. If both are set, both thresholds are applied. If neither is set, results are reported without threshold filtering. 🚪💨
  • pd_suppress_range_results — flag to suppress ranging results for PD requests. When set, the device performs ranging measurements to provide ranging services to a peer (e.g. in RSTA role) but does not report the measurement results to userspace. Only valid when request_type is NL80211_PMSR_FTM_REQ_TYPE_PD. 🤫

🌈 Description 🌈

See also nl80211 for the respective attribute documentation. 🦋

✨ SEE ALSO ✨

okay bestie, buckle up 💖 this is the part where we list, like, everything else in the kernel that vibes with struct cfg80211_pmsr_request_peer(9). It's a lot. Like, a LOT lot. But every single one is here, so grab a snack 🍓 and let's go.

First things first, the whole thing lives in the kernel file ./include/net/cfg80211.h — that's the mothership 🛸.

If you're new here, start with Introduction(9) and Device registration(9) so you actually know what's going on before you go deeper. That's the lore, fr fr.

🌸 the channel + rate girlies

Channels and rates, the ✨foundation✨ of literally everything wireless:

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

And the OBSS/he stuff, which is giving "I know my BSS colors":

  • struct ieee80211_he_obss_pd(9)
  • struct cfg80211_he_bss_color(9)

🎀 the capability crew (ht → vht → he → eht → uhr)

The way these stack up is iconic honestly, each generation handing the next one the aux cord:

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

🦋 edmg, s1g, and the band itself

Weird little bands, but they ate:

  • enum ieee80211_edmg_bw_config(9)
  • struct ieee80211_edmg(9)
  • struct ieee80211_sta_s1g_cap(9)
  • struct ieee80211_supported_band(9)

💅 sband helpers + freq limits

The getters and setters you'll actually be calling, plus the sibling that's "private" (the underscore is doing so much work):

🌈 Actions and configuration

Okay this section is huge, but it's the main character energy of the whole file, no cap. Start with Actions and configuration(9) itself, then:

  • 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 girlies (there are SO many)

Literally all of these are about channel definitions and whether they're valid, compatible, or usable. Obsessed:

🫶 survey, crypto, beacons, AP settings

The AP-side glow-up, from crypto settings all the way to color change:

  • 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 parameters my beloved 😭 the apply-mask enum, the tx power struct, all of it:

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

🔥 rate info + station info

Rate flags, rate bandwidth, and all the stats you could ever want:

  • 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 + get_station

Specific absorption rate stuff (yes, that SAR) plus the getter:

  • 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, mpath, mesh, ocb, txq

The odds and ends that lowkey matter a lot:

  • 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 is where half the drama happens tbh. Start at 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)

💜 auth / assoc / deauth / disassoc

The whole handshake arc, from auth to disassoc, plus ML reconf and IBSS:

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

🦋 wiphy params, PMKSA, wowlan, coalesce

The power-save / wake-up / coalescing corner of the universe:

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

NAN gets its own little kingdom and honestly? deserved 👑 start with 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, external auth, FTM, PMSR

This is literally the neighborhood of the struct you're reading about rn 🫶:

  • 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_request_peer(9)
  • struct cfg80211_pmsr_request(9)
  • struct cfg80211_update_owe_info(9)
  • struct mgmt_frame_regs(9)
  • struct cfg80211_ops(9)

💖 wiphy flags and interface combos

Interface limits, combinations, wowlan support, coalesce support — the whole capability buffet:

  • 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 lifecycle + locking

From priv to register to lock/unlock, this is the "how do I even make a wiphy" arc:

🌈 work + hrtimer work helpers

Queued work, delayed work, and the hrtimer variants. Pending, flush, cancel — the whole trio for each:

💅 ap reg power + wireless_dev

🌸 Utility functions

Little helpers that do a lot of heavy lifting behind the scenes. Start with Utility functions(9):

🦋 Data path helpers

Conversion + element-finding + RNR stuff. Start at Data path helpers(9):

🔥 Regulatory enforcement infrastructure

Rules are rules bestie, and the regdb said what it said. Start with Regulatory enforcement infrastructure(9):

And the internal ones — yes, "Internal" is in the name, so like, mind your business 🙈 these are Internal regulatory db functions(9):

💀 every notify + event function ever (basically)

The entire "tell the world something happened" lineup. Deep breath. 🫁

✨ RFkill integration

So your radio can actually be turned off, iconic:

🎀 Vendor commands

For when you need to do your own thing. Start at Vendor commands(9):

⭐ Test mode

Testing testing 1 2 3 🎤 Test mode(9) and friends:

🌈 connect / roam / disconnect / mgmt

The full social life of a station — connect, roam, authorize the port, disconnect, then immediately tell everyone:

and that's the whole list, bestie 🫶 go forth and read the docs, you got this 💅✨

okay so the SEE ALSO list keeps going and honestly? it's giving "the whole kernel API extended universe" 💅 every single one of these is a real page you can go read, so here's the rest of the roll call — no skips, no cap:

okay that's the entire cross-reference list, every single one, delivered with love 🧚 and now the lil sign-off: this whole page lives under ./include/net, it's dated October 2026, and the source/version footer on the bottom line is just the man page being like "struct cfg8...request_peer(9)" because even the footer got truncated for the aesthetic 💅 go read the other pages bestie, they're all here, periodt ✨👑

📦 where this page comes from