ENUM MPATH_INFO_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum mpath_info_flags(9) β€” mesh path information flags πŸ’…

okay so bestie, this is the Kernel API Manual page for enum mpath_info_flags, and it is literally the enum that tracks which mesh path info fields have been filled in. No cap. 🫢

✨ NAME ✨

enum mpath_info_flags β€” mesh path information flags. That’s the whole name, short and iconic. πŸ’–

πŸŽ€ SYNOPSIS πŸŽ€

enum mpath_info_flags {
    MPATH_INFO_FRAME_QLEN ,
    MPATH_INFO_SN ,
    MPATH_INFO_METRIC ,
    MPATH_INFO_EXPTIME ,
    MPATH_INFO_DISCOVERY_TIMEOUT ,
    MPATH_INFO_DISCOVERY_RETRIES ,
    MPATH_INFO_FLAGS ,
    MPATH_INFO_HOP_COUNT ,
    MPATH_INFO_PATH_CHANGE

};

🧚 Constants 🧚

okay these are the enum constants, and each one is a little flag saying β€œthis field got filled.” Slay:

  • MPATH_INFO_FRAME_QLEN β€” frame_qlen filled
  • MPATH_INFO_SN β€” sn filled
  • MPATH_INFO_METRIC β€” metric filled
  • MPATH_INFO_EXPTIME β€” exptime filled
  • MPATH_INFO_DISCOVERY_TIMEOUT β€” discovery_timeout filled
  • MPATH_INFO_DISCOVERY_RETRIES β€” discovery_retries filled
  • MPATH_INFO_FLAGS β€” flags filled
  • MPATH_INFO_HOP_COUNT β€” hop_count filled
  • MPATH_INFO_PATH_CHANGE β€” path_change_count filled

🌸 Description 🌸

Used by the driver to indicate which info in struct mpath_info it has filled in during get_station or dump_station. That’s the vibe check: the driver uses these flags to say which info is filled. πŸ’…

βœ¨πŸ’… SEE ALSO πŸ’…βœ¨

okay so literally every single one of these lives in the kernel file ./include/net/cfg80211.h β€” and yes bestie, I'm giving you the whole list, no skipping, no "you get the idea", we go all the way down 🫢

and that's the whole list, bestie β€” nothing dropped, nothing merged, we ate and left no crumbs πŸŽ€πŸ’–βœ¨

okay so the cross-reference list literally does not stop, and honestly? that's main character energy. here's the rest of the SEE ALSO crew, in exactly the order the page gives them 🫢

beaconing, channel switches, and a whole little conversion circle between operating classes and chandefs β€” it's giving "we know a guy for every format" ✨

note how cfg80211_register_netdevice(9) and cfg80211_unregister_netdevice(9) are right there next to each other, iconic sibling behavior, one puts it in and one takes it out πŸ’…

a whole stop squad in there β€” cfg80211_stop_link(9), cfg80211_stop_iface(9), and the big one cfg80211_shutdown_all_interfaces(9), bestie is NOT playing around 😭

one to set it, one to ask about it. delulu is not the solulu, checking is πŸŽ€

a whole NAN friend group, we love a themed cluster 🌸

like, the color-change notifications alone are a trilogy β€” started, aborted, and the plain one β€” plus a collision notify, because drama finds a way πŸ™ˆ and wiphy_locked_debugfs_read(9) / wiphy_locked_debugfs_write(9) are your locked debugfs duo, matching set, obsessed.


and that's a wrap on the whole page, bestie πŸŽ€ every single cross-reference accounted for, no skips, no vibes-based omissions, periodt.

so quick cute sign-off about where this bad girl came from: the footer tells us the source lives under ./include/net, the date on it is October 2026, and the page itself is the man page for enum mpath_info_flags(9). go forth and wifi responsibly πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from