STRUCT MPATH_INFO(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 struct mpath_info(9) — mesh path information 🌸

okay so bestie, welcome to struct mpath_info(9) from the Kernel API Manual ✨ this is the little glow-up struct that carries all the tea about a mesh path — literally everything the kernel knows about how to get from here to your destination 🦋

✨ SYNOPSIS ✨

here's the whole vibe, character for character, no cap:

struct mpath_info {
    u32 filled;
    u32 frame_qlen;
    u32 sn;
    u32 metric;
    u32 exptime;
    u32 discovery_timeout;
    u8 discovery_retries;
    u8 flags;
    u8 hop_count;
    u32 path_change_count;
    int generation;
 };

🎀 Members 🎀

these are the fields and honestly? each one is kind of iconic in its own way 💅

  • filled — a bitfield of flags from enum mpath_info_flags ✨ like a little checklist of which fields actually got filled in, iykyk
  • frame_qlen — number of queued frames for this destination 📬 these are the frames literally waiting in line, main character energy, very patient
  • sn — target sequence number 🔢
  • metric — metric (cost) of this mesh path 💸 the price of getting where you're going, and yes we're judging it
  • exptime — expiration time for the mesh path from now, in msecs ⌛ starts counting from now, msecs, don't forget
  • discovery_timeout — total mesh path discovery timeout, in msecs ⏰ the whole discovery saga's time limit
  • discovery_retries — mesh path discovery retries 🔁 how many times we're willing to try again
  • flags — mesh path flags from enum mesh_path_flags 🚩
  • hop_count — hops to destination 🐇 how many hops, literally
  • path_change_count — total number of path changes to destination 🔄 every single time this path switched up, counted
  • generation — generation number for nl80211 dumps. This number should increase every time the list of mesh paths changes, i.e. when a station is added or removed, so that userspace can tell whether it got a consistent snapshot 👑
lowkey important bestie: that generation field is the vibe check for your snapshot 🌈 it should increase every time the list of mesh paths changes — like when a station is added or removed — so userspace can tell whether it got a consistent snapshot. if it didn't bump, you might be looking at stale tea 💀

💖 Description 💖

Mesh path information filled by driver for get_mpath and dump_mpath. ✨ that's the whole thing — the driver fills this bad boy in so those two can do their thing 🫶

more coming, bestie — don't go anywhere 💜

💖 SEE ALSO 💖

okay bestie, deep breath. The SEE ALSO on this one is not a little list, it's a whole cinematic universe — literally the entire cfg80211 extended family showed up to the group chat, and not one of them is getting left on read. Every single one is below, in order, untouched. Scroll gang, this one's for you 🫶

Start with the source file itself, plus the two intros you'll want first:

  • Kernel file ./include/net/cfg80211.h
  • Introduction(9)
  • Device registration(9)

Then we get the channel / rate / BSS enum besties and the whole capability-cap parade 💅

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

and the functions that hang with them, including the one with the leading underscore (yes, keep the underscore, she's shy but she's real):

Now the actions-and-configuration arc, aka the chandef girls' main character era ✨

Survey, crypto, MBSSID, beacon, AP settings, station params, mesh, OCB and txq — truly the "we contain multitudes" section of the list 🌸

  • 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)
  • 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)
  • enum monitor_flags(9)
  • enum mpath_info_flags(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)

ngl the scanning and BSS list handling crew is lowkey huge, and then it rolls straight into connect, wowlan, coalesce, gtk rekey, mgmt tx and qos map — obsessed 😭

  • 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 says hi (full name and all, don't abbreviate her), then PMK/external auth/FTM/PMSR, then the wiphy structs and ops 💜

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

The wiphy saga: flags, iface limits/combos, wowlan support, vendor command flags, opmode, radio stuff, NAN capa, and then the actual wiphy + friends 🔥

Utility functions time — channel math, hdrlen helpers, radiotap iterator, and then the data path helpers, all the find_ie family, RNR iteration, defragmenting and layer 2 updates 🦋

Regulatory enforcement infrastructure + internal regulatory db functions, the serious girlies of the list 👑

Scan done / scan results / BSS informing and the BSS refcount-and-iter squad, then MLME rx/tx, mic failure, ibss joined and new peer candidate 🎀

RFkill integration, vendor commands and test mode — three whole little squads 😌

And the final stretch 💀 — connect/roam/disconnect reporting, remain-on-channel, tid stats, sta add/del, rx mgmt + tx status, control port, cqm notifications, radar, cac, gtk rekey, pmksa candidate, spurious/unexpected frames, probe status, obss beacon reports, and one last struct:

…and the SEE ALSO roll call keeps going, bestie. It’s giving “kernel wiki rabbit hole” energy 🌀 — grab a snack and let’s finish the list 💅:

That’s the whole list and the whole page, bestie 🌈💖. The source/version is ./include/net, the date is October 2026, and the page is struct mpath_info(9). Go be iconic with your wireless structs, and remember: hydrate and read your man pages 💅✨

📦 where this page comes from