rte_table_...qinq_pppoe(3)

✨ NAME ✨

rte_table_encap_ether_qinq_pppoe — bestie, this is a struct page from the DPDK library manual (the "Library Functions Manual" one 🫶), and it's literally just a little bundle of headers you'd slap onto a packet when you're doing QinQ + PPPoE encapsulation. Iconic behavior, honestly.

---

🌸 SYNOPSIS 🌸

#include <rte_table_action.h>

🎀 Data Fields 🎀

• struct rte_table_action_ether_hdr ether
• struct rte_table_action_vlan_hdr svlan
• struct rte_table_action_vlan_hdr cvlan
• struct rte_table_action_pppoe_hdr pppoe

---

💅 Detailed Description 💅

It's giving… QinQ_PPPoE encap parameters. That's the whole vibe. Four header structs, one dream. ✨

Definition at line 534 of file rte_table_action.h.

---

🦋 Field Documentation 🦋

struct rte_table_action_ether_hdr ether

Ok so heads up: this one is only valid when type is set to QinQ. Not me warning you ahead of time so you don't get weird output 😭

Definition at line 537 of file rte_table_action.h.

struct rte_table_action_vlan_hdr svlan

The Service VLAN header. Yes bestie, the S in svlan really does stand for Service. SLAY. 💖

Definition at line 538 of file rte_table_action.h.

struct rte_table_action_vlan_hdr cvlan

The Customer VLAN header. Cute, cozy, customer-facing. The way these two VLAN headers stack is the whole point of QinQ, iykyk. 🧚

Definition at line 539 of file rte_table_action.h.

struct rte_table_action_pppoe_hdr pppoe

The PPPoE/PPP headers — both of them living in one field, sharing, which is honestly kind of them. 🌈

Definition at line 540 of file rte_table_action.h.

---

👑 Author 👑

Generated automatically by Doxygen for DPDK from the source code. So technically no human author to thank, just the machine doing its little thing. Respect. 💀

---

fr fr, the one thing to remember: that ether field only counts when type is QinQ. Everything else is just VLANs and PPPoE doing their iconic little stack. 🍓

and that's a wrap on this page, babes — DPDK Version 25.11.3, rte_table_...qinq_pppoe(3), mwah 💋