rte_flow_item_icmp6(3)

✨ rte_flow_item_icmp6 ✨

okay bestie, gather round, because today we're talking about rte_flow_item_icmp6 from the DPDK crew πŸ’– it lives in the Library Functions Manual, it's giving very niche-but-iconic, and it's literally the struct you reach for when you want a flow rule to match ICMPv6 headers. no cap.


🌸 NAME 🌸

rte_flow_item_icmp6 β€” the ICMPv6 item struct, here to vibe check your packets πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <rte_flow.h>

πŸŽ€ Data Fields πŸŽ€

  • uint8_t type
  • uint8_t code
  • uint16_t checksum

πŸ’– Detailed Description πŸ’–

RTE_FLOW_ITEM_TYPE_ICMP6

Matches any ICMPv6 header. that's it, that's the whole job, and it does it flawlessly fr fr πŸ‘‘

Defined at line 1467 of file rte_flow.h. yes, we cite our sources in this household πŸ“–βœ¨


🧚 Field Documentation 🧚

⭐ uint8_t type

ICMPv6 type. that's the field telling you what kind of ICMPv6 message we're dealing with 🫢

Defined at line 1468 of file rte_flow.h.

🌈 uint8_t code

ICMPv6 code. the lil sub-detail that rides along with the type, the supporting character with main character energy πŸ’…

Defined at line 1469 of file rte_flow.h.

πŸ“ uint16_t checksum

ICMPv6 checksum. the integrity girlie, making sure nobody messed with your header on the way over πŸ›‘οΈβœ¨

Defined at line 1470 of file rte_flow.h.


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for DPDK from the source code. not a human typing this out by hand, a whole machine doing it, and honestly? slay πŸ€–πŸ’–


lowkey reminder: every single line number, field name, and type above is exactly as written in rte_flow.h. don't go paraphrasing those in your code, bestie, the compiler will notice 😭

and that's the whole page, periodt πŸ’… this was DPDK, Version 25.11.3, signing off from the rte_flow_item_icmp6(3) manual page. go match some ICMPv6 headers, you absolute icon πŸŽ€πŸ¦‹βœ¨

πŸ“¦ where this page comes from