mesh_path_fix_nexthop(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the mesh_path_fix_nexthop(9) page from the Kernel API Manual β€” it's short, it's specific, and it's lowkey iconic for doing exactly one thing. Let's go 🫢

🌸 NAME 🌸

mesh_path_fix_nexthop β€” force a specific next hop for a mesh path. That's the whole vibe πŸ’…

✨ SYNOPSIS ✨

void mesh_path_fix_nexthop (struct mesh_path *mpath , struct sta_info *next_hop );

πŸŽ€ ARGUMENTS πŸŽ€

  • mpath β€” the mesh path to modify. This is the path you're changing, no cap.
  • next_hop β€” the next hop to force. You're literally forcing this one to be the next hop, periodt.

πŸ¦‹ DESCRIPTION πŸ¦‹

Locking: this function must be called holding mpath->state_lock

Okay so the locking note is the whole entire moment here: this function must be called holding mpath->state_lock. That's not a suggestion, bestie β€” it's the rule. Hold the lock, then do the thing. πŸ”’

🐚 SEE ALSO 🐚

Kernel file ./net/mac80211/mesh_pathtbl.c is the source location mentioned here. Also these cuties:


That's the whole page, bestie. Cute little sign-off: source ./net/mac80211, date October 2026, and the header is mesh_path_fix_nexthop(9) πŸŽ€βœ¨

πŸ“¦ where this page comes from