batadv_mcast...tr_flags_get(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 batadv_mcast...tr_flags_get(9) 🌸

okay so bestie, welcome to the Kernel API Manual — yes that's the manual name, we're fancy now 💅 — and today's main character is batadv_mcast_mla_rtr_flags_get. It's a little function that just wants to know: are there multicast routers around or not? Let's get into it 🫶

✨ NAME ✨

batadv_mcast_mla_rtr_flags_get — get multicast router flags 🎀

✨ SYNOPSIS ✨

u8 batadv_mcast_mla_rtr_flags_get (struct batadv_priv *bat_priv , struct
net_device *bridge );

like, it takes two things and hands you back a u8, no big deal ✨

✨ ARGUMENTS ✨

  • bat_priv — the bat priv, aka the whole vibe bundle with all the mesh interface information in it 💖
  • bridge — the bridge interface sitting on top of the mesh_iface if there even is one, otherwise you just pass NULL and it's fine, no cap 🙈

✨ DESCRIPTION ✨

So what does it actually do? It checks whether IPv4 and IPv6 multicast routers are present on this node, or chilling behind its bridge 🌈

That's the whole thing. Checks presence, reports back. Periodt 💅

✨ RETURN ✨

here's what the flags mean, bestie, memorize them iykyk 🔥

  • BATADV_NO_FLAGS — both an IPv4 and IPv6 multicast router is present 👑 (iconic, honestly)
  • BATADV_MCAST_WANT_NO_RTR4 — no IPv4 multicast router is present 💀
  • BATADV_MCAST_WANT_NO_RTR6 — no IPv6 multicast router is present 😭
  • the former two OR'd — no multicast router is present at all 🫠
ngl the last one is just the first two flags smooshed together with an OR, so like... zero routers, zero problems? or all the problems. vibe check it yourself 🧚

✨ SEE ALSO ✨

Kernel file ./net/batman-adv/multicast.c — that's where the magic lives ✨ and here's the entire squad, the full roster, not a single one skipped because we don't do that here 💜

and that's the whole page bestie, go forth and check those router flags 🦋

this little gem came from ./net/batman-adv, dated October 2026 — mwah, stan, bye 💋

📦 where this page comes from