mesh_path_send_to_gates(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mesh_path_send_to_gates(9) πŸ’…

okay so bestie, we're in the Kernel API Manual today and this one's a little networking baddie from the mesh world. let me put you on. ✨


πŸŽ€ NAME πŸŽ€

mesh_path_send_to_gates β€” literally sends those pending frames off to all the known mesh gates. no gate left behind, periodt. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

int mesh_path_send_to_gates (struct mesh_path *mpath );

🌸 ARGUMENTS 🌸

  • mpath β€” the mesh path whose queue is about to get emptied. yeah, that one. she's the main character of this function and her queue is getting cleared out. 🫢

πŸ’« DESCRIPTION πŸ’«

so here's the tea, and it's honestly kind of elegant:

if there's only one gate, the frames get transferred from the failed mpath queue over to that gate's queue. simple. one gate, one destination, slay. πŸ’…

but if there's more than one gate? now we're doing the little relay thing β€” the frames are copied from each gate to the next one along. icon behaviour honestly. 🧚

and then, after the frames are copied, the mpath queues are emptied onto the transmission queue. bye bestie, go get transmitted. ✨


πŸ”₯ RETURN πŸ”₯

  • 0 on success πŸŽ‰
  • -EHOSTUNREACH 😭

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file ./net/mac80211/mesh_pathtbl.c and all her friends:

like genuinely go read them, they're all in the group chat. πŸ’œ


aaaand that's the page! πŸŽ€ this one came at you from the source ./net/mac80211, dated October 2026 β€” catch you on the next one, bestie, mwah πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from