batadv_batman_skb_recv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… batadv_batman_skb_recv β€” like, the whole manual page, bestie

okay so this is batadv_batman_skb_recv(9) from the Kernel API Manual, and no cap it's giving "the front door of the batman-adv receive path" πŸ¦‹ β€” it handles an incoming message from a hard interface. yes, hard interface, that's the actual term, we don't make the rules. anyway let's get into it ✨


✨ SYNOPSIS ✨

int batadv_batman_skb_recv (struct sk_buff *skb , struct net_device *dev
, struct packet_type *ptype , struct net_device *orig_dev );

four args, all pointers, returns an int. she's compact, she's iconic, she's not here to waste your time πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • skb β€” the received packet, aka the actual goods πŸ“¦ the packet that just showed up.
  • dev β€” the net device that the packet was received on. like, which interface caught it.
  • ptype β€” packet type of the incoming packet, and yeah, it's ETH_P_BATMAN. that's the whole vibe check right there πŸ”₯
  • orig_dev β€” the original receive net device (e.g. a bonded device). so if the packet took a little detour through a bond, this is where it actually came from, iykyk 🧚

🫢 RETURN 🫢

It returns NET_RX_SUCCESS on success, or NET_RX_DROP in case of failure.

that's it. two outcomes. slay or yeet. πŸ’€


🌈 SEE ALSO 🌈

Kernel file ./net/batman-adv/main.c, plus the whole friend group:

literally the entire main.c extended universe, go read them, they're all main character energy πŸ‘‘


okay that's the page!! huge shoutout to ./net/batman-adv for the source and the October 2026 date on this one β€” she's from the future, she's thriving, periodt β­πŸ’–

πŸ“¦ where this page comes from