rte_l2tpv2...ith_offset(3)

✨ NAME ✨

rte_l2tpv2_msg_with_offset — okay bestie, this is a lil struct that holds the options offset size and the offset padding from an L2TPv2 message header 🎀

It lives in section 3 of the Library Functions Manual, so yes, this is a function/API-adjacent kind of page, and no, you can't just run it in your shell 💅

---

🦋 SYNOPSIS 🦋

#include <rte_l2tpv2.h>

🎀 Data Fields 🎀

rte_be16_t tunnel_id
rte_be16_t session_id
rte_be16_t offset_size
uint8_t * offset_padding

not me showing you the whole field list up top and then explaining it all again below 💀 stay with me, that's just how man pages do

---

🌸 DETAILED DESCRIPTION 🌸

So the L2TPv2 message Header contains the options offset size and the offset padding, and this struct is literally that — it's giving "just the offset bits, nothing else" ✨

Definition at line 179 of file rte_l2tpv2.h.

---

💖 FIELD DOCUMENTATION 💖

🌈 rte_be16_t tunnel_id

tunnel ID, and it's 16 bits bestie — <italic>(16)</italic> ✨

Definition at line 180 of file rte_l2tpv2.h.

🌈 rte_be16_t session_id

session ID, also 16 bits <italic>(16)</italic> 🫶

Definition at line 181 of file rte_l2tpv2.h.

🌈 rte_be16_t offset_size

offset size, 16 bits again <italic>(16)</italic> 💅

Definition at line 182 of file rte_l2tpv2.h.

🌈 uint8_t* offset_padding

offset padding, and this one's <italic>(variable length)</italic> — the only field here that isn't a tidy little 16-bit situation, so clock it 👑

Definition at line 183 of file rte_l2tpv2.h.

---

👑 AUTHOR 👑

Generated automatically by Doxygen for DPDK from the source code. No human hand-wrote this prose, which honestly explains a lot and yet she still ate 😭✨

---

🫶 that's the whole page, no cap — every field, every line number, every <italic>(16)</italic>, untouched

DPDK — Version 25.11.3 💖 thanks for reading my little man page bestie, go forth and parse L2TPv2 headers, mwah 🎀🦋🌸