STRUCT CFG80211_FTM_RESPONDER_STATS(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 NAME 🎀

struct cfg80211_ftm_responder_stats — FTM responder statistics ✨

(this is a Kernel API Manual page btw, so like… kernel API vibes, iykyk 💅)

🌸 SYNOPSIS 🌸

struct cfg80211_ftm_responder_stats {
    u32 filled;
    u32 success_num;
    u32 partial_num;
    u32 failed_num;
    u32 asap_num;
    u32 non_asap_num;
    u64 total_duration_ms;
    u32 unknown_triggers_num;
    u32 reschedule_requests_num;
    u32 out_of_window_triggers_num;
 };

okay so literally that's the whole struct, bestie — it's giving "receipts for your FTM responder era" 🧾✨ every single field is a counter or a flag, no cap.

👑 MEMBERS 👑

every one of these is a member of the struct and each one is doing its own lil job 🫶 let's get into it:

  • filled — a bitflag of flags, using the bits of enum nl80211_ftm_stats, to indicate which values in this struct are actually relevant for them. so like… it's the vibe check that tells you which numbers below you should even care about 🔥
  • success_num — the number of FTM sessions in which all frames were successfully answered. full slay, zero notes 💯
  • partial_num — the number of FTM sessions in which part of the frames were successfully answered. so like… it tried, ok? 🥲 half-ate, no shade
  • failed_num — the number of failed FTM sessions. it's giving flop era, but we still count them 💀
  • asap_num — the number of ASAP FTM sessions. fast fast fast 🏃‍♀️💨
  • non_asap_num — the number of non-ASAP FTM sessions. these ones are chill, no rush 🦋
  • total_duration_ms — total sessions durations. this one "gives an indication of how much time the responder was busy" — so basically it's the clock telling you how booked and busy the responder was 👑⏱️
  • unknown_triggers_num — number of unknown FTM triggers, i.e. triggers from initiators that didn't finish successfully the negotiation phase with the responder. messy, unresolved, left on read 🙈
  • reschedule_requests_num — number of FTM reschedule requests, where the initiator asks for a new scheduling although it already has scheduled FTM slot. bestie already HAS a slot and is still asking for another one 😭 main character behavior fr
  • out_of_window_triggers_num — total FTM triggers out of scheduled window. showing up outside the agreed time like 🫠 iconic but wrong

okay that's the full member list for this part — more of this page is coming so stay tuned bestie 💜

🌈 SEE ALSO 🌈

okay bestie, this SEE ALSO list is giving entire cfg80211 extended universe 😭💖 it's huge. like, not me scrolling for ten years. grab a boba, we're listing every single one exactly, no cap:

okay bestie that's the whole see-also universe, every single one of them, no skips 💅 if a name up there looks like your fave, go read its page next, it's literally right there.

tiny reminder that this whole list is cross-reference only — nothing here changes what struct cfg80211_ftm_responder_stats does, it's just the friend group around it 🫶

and that's a wrap on the page!! 🎀 this one lives in ./include/net, it's dated October 2026, and the header labels it struct cfg8...ponder_stats(9). go forth and slay your FTM responder stats, mwah 💖✨

📦 where this page comes from