PROBE::UDP.RECVMSG(3stap)

πŸ’Œ PROBE::UDP.RECVMSG(3stap) β€” the Networking Tapset glow-up

okay bestie, gather round, because this is probe::udp.recvmsg.return and she is literally the moment your UDP message finally lands πŸ’–


✨ NAME ✨

probe::udp.recvmsg.return β€” fires whenever an attempt to receive a UDP message is completed πŸŽ€

like. the second the receive attempt wraps up, this probe is there, front row, main character energy πŸ‘‘


🌸 SYNOPSIS 🌸

probe udp.recvmsg.return {}

that's it. that's the whole vibe. no args, no fuss, just a lil probe waiting to pop off ✨


πŸ¦‹ VALUES πŸ¦‹

every one of these cuties is available to you inside the probe handler, no cap:

  • daddr β€” a string representing the destination IP address 🫢
  • sport β€” UDP source port πŸ’…
  • dport β€” UDP destination port πŸŽ€
  • saddr β€” a string representing the source IP address 🌸
  • family β€” IP address family 🌈
  • size β€” number of bytes received by the process πŸ“
  • name β€” the name of this probe 🏷️
yes, both saddr and daddr are strings, and yes, both ports are just numbers. slay. keep the types straight and you're golden ⭐

🧚 CONTEXT 🧚

the process which received a UDP message πŸ‘‘ β€” that's your context, that's your girl, that's who you're profiling when this probe goes off.


πŸ’œ SEE ALSO πŸ’œ


and that's the whole page, bestie!! πŸ’–

this was the SystemTap Tapset Reference, version line vibes, dated September 2026 πŸŽ€ β€” go forth, tap that UDP traffic, and remember: not me explaining kernel probes at 3am, iykyk πŸ’…βœ¨

πŸ“¦ where this page comes from