rte_flow_i...e_proto_id(3)

📦 version 26.03, in nixos 26.05, nixpkgs unstable

💖 NAME 💖

rte_flow_item_pppoe_proto_id — okay bestie, this is the manual page for it, yes the whole page is named after one struct, and honestly? iconic of it.

So this page lives in the DPDK docs, section 3 of the Library Functions Manual, and it's all about this one little flow item. Let's get into it 🫶

✨ SYNOPSIS ✨

Like literally just include the header and you're in:

#include <rte_flow.h>

🎀 Data Fields

  • rte_be16_t proto_id — the one and only field, and yes she's the main character 💅 (details below, keep reading)

🦋 Detailed Description 🦋

So <pink>RTE_FLOW_ITEM_TYPE_PPPOE_PROTO_ID</pink> — that's the vibe check, that's the whole thing.

It matches a PPPoE optional proto_id field. That's it, that's the job 🌸

Heads up: it only applies to PPPoE session packets. Not all the packets. Just the session ones. No cap 💀

Normally it's preceded by any of:

  • RTE_FLOW_ITEM_TYPE_PPPOE
  • RTE_FLOW_ITEM_TYPE_PPPOE_PROTO_ID

(Yes, it can be preceded by itself. That's not a typo, it's literally in the doc. Not me inventing lore 🔥)

And for the record-keepers: Definition at line 1677 of file rte_flow.h. 📍

🌸 Field Documentation 🌸

💅 rte_be16_t proto_id

PPP protocol identifier 💖 that's the whole description, short and slay.

Definition at line 1678 of file rte_flow.h. 📍

🌈 Author 🌈

Generated automatically by Doxygen for DPDK from the source code. 🧚 Not a human, a whole bot, and it ate ✨

Alright bestie, that's the page 🎀 — brought to you by DPDK, Version 26.03.0, and that header/footer situation was rte_flow_i...e_proto_id(3) in case you needed to cite it. Go forth and match those PPPoE session packets 💜🦋

📦 where this page comes from