tipc_l2_rcv_msg(9)

📦 version 7.3.1, in nixpkgs unstable

💖 tipc_l2_rcv_msg — like, the TIPC inbound bouncer 💖

okay so bestie, this is a page from the Kernel API Manual and it's all about tipc_l2_rcv_msg, which handles incoming TIPC messages from an interface. yes it's kernel networking. yes you're gonna understand it. let's go 🫶

✨ SYNOPSIS ✨

int tipc_l2_rcv_msg (struct sk_buff *skb , struct net_device *dev ,
       struct packet_type *pt , struct net_device *orig_dev );

that's the whole vibe. one function, four args, returns an int. iconic.

🎀 ARGUMENTS 🎀

  • skb — the received message itself, aka the actual packet that just showed up 💌
  • dev — the net device that the packet was received on, like the door it walked in through 🚪
  • pt — the packet_type structure which was used to register this handler, iykyk, it's the registration receipt 🧾
  • orig_dev — the original receive net device in case the device is a bond, so if things got bonded together, this is the OG device 💍

🌸 DESCRIPTION 🌸

so what does it actually do? it accepts only packets explicitly sent to this node, or broadcast packets. that's it, that's the whole gatekeeping philosophy. queen behavior tbh 👑

and the way it's picky?? it ignores packets sent using interface multicast, and it also ignores traffic sent to other nodes — which can happen if the interface is running in promiscuous mode. so yeah, promiscuous mode can sneak extra traffic in and this function is just like "not for me bestie, moving on" 💅

no cap: if you were hoping it would pick up multicast or other-node traffic, it will not. it literally says it ignores those. periodt.

🦋 SEE ALSO 🦋

the kernel file ./net/tipc/bearer.c and its whole friend group:

go read them, they're all in ./net/tipc together, one big happy bearer.c family 🌈

⭐ little sign-off ⭐

this cutie of a page came from the source path ./net/tipc, dated October 2026, and it's living in the Kernel API Manual. that's the whole footer, no secrets here 🔥

stay hydrated, read your kernel source, and remember: only explicitly-sent-to-this-node or broadcast packets get in 💖✨🎀

📦 where this page comes from