batadv_mcast_bridge_log(9)

📦 version 7.3.1, in nixpkgs unstable

💅 batadv_mcast_bridge_log

okay so first things first: this little cutie lives in the Kernel API Manual, and it's a kernel-doc page for batadv_mcast_bridge_log(9). she's a debug-logging icon, no cap ✨

🌸 NAME

batadv_mcast_bridge_log — debug output for topology changes in bridged setups 🫶

✨ SYNOPSIS

void batadv_mcast_bridge_log (struct batadv_priv *bat_priv , struct batadv_mcast_mla_flags *new_flags );

🎀 ARGUMENTS

  • bat_priv — the bat priv with all the mesh interface information 💖 like, it's the whole vibe of the mesh interface, everything lives in there
  • new_flags — flags indicating the new multicast state ⭐ these are the freshly-baked flags, the new fit

🦋 DESCRIPTION

okay so bestie, here's the tea ☕

If no bridges are ever used on this node, then this function does nothing. literally nothing. it just sits there. main character energy of doing absolutely zero 🧚

Otherwise, this function outputs debug information to the 'mcast' log level which might be relevant to our multicast optimizations 🔥 (note the might — she's not making promises, she's just logging).

More precisely — and this is the good part — it outputs information when a bridge interface is added or removed from a mesh interface 👑 And when a bridge is present, it further outputs information about the querier state, which is relevant for the multicast flags this node is going to set 🌈

so like: bridge goes in? we log. bridge goes out? we log. bridge stays? we log about the querier state bc it matters for the flags. that's the whole gig 💅

💜 SEE ALSO

the whole squad, roll call time 🎀 — and the kernel file is ./net/batman-adv/multicast.c:

that's the post 💌 this page is from ./net/batman-adv, dated October 2026 — mwah, go read the source, ily, bye 🫶✨

📦 where this page comes from