STRUCT NFP_TUN_REQ_ROUTE_IPV4(9)

💖 struct nfp_tun_req_route_ipv4(9) — the Kernel API Manual, bestie edition 💖

Okay so you're looking at struct nfp_tun_req_route_ipv4, which is a Kernel API Manual page, and honestly? It's a little cutie. It's the struct NFP uses when it's requesting a route or neighbour lookup. That's the whole vibe. Let's get into it 🎀

---

✨ NAME ✨

struct nfp_tun_req_route_ipv4 — NFP requests a route/neighbour lookup. That's literally it, that's the whole job, and it does it slayfully 💅

---

🌸 SYNOPSIS 🌸

Here's the shape of her, no cap — copy it exactly:

struct nfp_tun_req_route_ipv4 {
    __be32 ingress_port;
    __be32 ipv4_addr;
    __be32 reserved[2];
 };

Three fields, all __be32, look at her go ✨

---

🦋 Members 🦋

• ingress_port — the ingress port of the packet that signalled the request. Like, which door did this packet walk in through 🚪
• ipv4_addr — the destination ipv4 address for the route. Where it's headed, iykyk 🗺️
• reserved — reserved for future use. She's just sitting there holding space for future content, main character energy fr fr 👑

---

🔥 SEE ALSO 🔥

The Kernel file lives right here at ./drivers/net/ethernet/netronome/nfp/flower/tunnel_conf.c — go say hi 🫶

And the whole friend group, in order:

• struct nfp_tun_pre_tun_rule(9)
• struct nfp_tun_active_tuns(9)
• struct nfp_tun_active_tuns_v6(9)
• struct nfp_tun_req_route_ipv6(9)
• struct nfp_offloaded_route(9)
• struct nfp_tun_ipv4_addr(9)
• struct nfp_ipv4_addr_entry(9)
• struct nfp_tun_ipv6_addr(9)
• struct nfp_tun_mac_addr_offload(9)
• struct nfp_neigh_update_work(9)
• struct nfp_tun_offloaded_mac(9)

---

💀 Real talk for a sec: reserved is literally reserved for future use, so don't go writing your own lore into it, okay? Leave her be. 🙈

---

And that's the page, bestie! Signing off from ./drivers/net/ethernet/netrono..., dated October 2026, under the title struct nfp_...q_route_ipv4(9) — the truncated names are still iconic, we love a mysterious queen 🌈⭐💜 🧚🍓