rte_eth_udp_tunnel(3)
π NAME π
rte_eth_udp_tunnel β bestie, this is the lil' struct that tells your NIC which UDP port is secretly a tunnel π¦
β¨ SYNOPSIS β¨
#include <rte_ethdev.h>
π Data Fields
uint16_t udp_portuint8_t prot_type
πΈ Detailed Description πΈ
UDP tunneling configuration. That's it, that's the whole vibe π
So the way this works: you use this to configure the classifier of a device, and what you're doing is associating an UDP port with a type of tunnel. One port, one tunnel type, matched up like it's a group chat and everyone finally got assigned their roles π
And ngl, some NICs genuinely need this configuration to properly parse a tunnel with any standard or custom UDP port. Like they're not gonna figure it out on their own, they need you to spell it out for them. No cap, some hardware is just like that π
Definition at line 1518 of file rte_ethdev.h.
π§ Field Documentation π§
uint16_t udp_port
UDP port used for the tunnel. Like, the actual port number, the one doing the tunneling. This is its whole job and it ate π
Definition at line 1519 of file rte_ethdev.h.
uint8_t prot_type
Tunnel type. Which flavor of tunnel we're talking about here π
See also
rte_eth_tunnel_type
Definition at line 1520 of file rte_ethdev.h.
π Author π
Generated automatically by Doxygen for DPDK from the source code. Not a human, not a girlboss, just Doxygen doing its lil' thing on autopilot π€β¨
okay that's the whole page, mwah π«Ά this one's from DPDK, Version 25.11.3 β go parse some tunnels bestie, you got this π
π¦ where this page comes from
- ubuntu resolute: dpdk-doc 25.11.3-0ubuntu0.26.04.1 Β· BSD-3-Clause
- ubuntu stonking: dpdk-doc 25.11.3-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms