batadv_mcast...hif_get_ipv4(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– batadv_mcast...hif_get_ipv4(9) πŸ’–

okay so this is a page from the Kernel API Manual and bestie, it's a whole little function with a whole lot of friends. it's batadv_mcast_mla_meshif_get_ipv4 β€” the meshif IPv4 multicast listener collector. yes, that's a mouthful, we're gonna get through it together 🫢


✨ NAME ✨

batadv_mcast_mla_meshif_get_ipv4 β€” get meshif IPv4 multicast listeners πŸ’…


🌸 SYNOPSIS 🌸

int batadv_mcast_mla_meshif_get_ipv4 (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, like, the main character of this whole operation πŸ’–
  • mcast_list β€” a list to put the found addresses into, it's the bag we're filling up πŸ“
  • flags β€” flags indicating the new multicast state, iykyk ⭐

πŸ¦‹ DESCRIPTION πŸ¦‹

so what this does is it collects the multicast addresses of IPv4 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. literally right here. no cap. πŸ‘‘


πŸ”₯ RETURN πŸ”₯

  • -ENOMEM on memory allocation error 😭 (the classic)
  • otherwise, the number of items added to the mcast_list ✨

πŸ’œ SEE ALSO πŸ’œ

first up, the kernel file itself: ./net/batman-adv/multicast.c β€” go read it, it's giving source of truth πŸ“–

then, the whole entire friend group (yes, all of them, I'm not skipping a single one, we don't do that here) 🧚:

like I said. the whole group chat. πŸ’€


that's the page, bestie! this one's from ./net/batman-adv, dated October 2026, and it's filed as batadv_mcast...hif_get_ipv4(9) β€” go forth and collect those listeners πŸ¦‹πŸ’–βœ¨

πŸ“¦ where this page comes from