batadv_mcast_mla_meshif_get(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 batadv_mcast_mla_meshif_get(9) 🌸

hiii bestie, welcome to the Kernel API Manual page for batadv_mcast_mla_meshif_get(9) 💖 this one is all about grabbing meshif multicast listeners, and yes, it's giving kernel-internals main character energy.

🎀 NAME 🎀

batadv_mcast_mla_meshif_get — get meshif multicast listeners. That's the vibe, periodt.

✨ SYNOPSIS ✨

int batadv_mcast_mla_meshif_get (struct net_device *dev , struct
       hlist_head *mcast_list , struct batadv_mcast_mla_flags *flags );

🦋 ARGUMENTS 🦋

  • dev — the device we're collecting multicast addresses from, bestie.
  • mcast_list — a list to put the found addresses into. Like a little collection basket 🧺
  • flags — flags indicating the new multicast state. Very flags. Much state.

💅 DESCRIPTION 💅

Okay so this function collects multicast addresses of multicast listeners residing on this kernel on the given mesh interface, dev, and drops them into the given mcast_list ✨ In general, multicast listeners provided by your multicast receiving applications run directly on this node — right here, on this very node, no cap.

If there's a bridge interface on top of dev, collect from that one instead. Just like with IP addresses and routes, multicast listeners will(/should) register to the bridge interface instead of an enslaved bat0. That's literally the rule, iykyk 👑

🔥 RETURN 🔥

-ENOMEM on memory allocation error, or the number of items added to the mcast_list otherwise. Slay 💀✨

👑 SEE ALSO 👑

Kernel file: ./net/batman-adv/multicast.c

The whole batman-adv multicast extended family is popping off here:

mwah 💋 this little page comes from ./net/batman-adv, October 2026, and it's literally the batadv_mcast_mla_meshif_get(9) page, bestie 🫶

📦 where this page comes from