STRUCT NFP_TUN_REQ_ROUTE_IPV6(9)
π STRUCT NFP_TUN_REQ_ROUTE_IPV6(9) π
okay so bestie, welcome to the Kernel API Manual π β yes this is one of those pages, a struct page, and honestly? kind of iconic. it's giving "small but does one very specific thing really well" energy and i'm obsessed.
β¨ NAME β¨
struct nfp_tun_req_route_ipv6 β the little struct where NFP goes "hey bestie, can u do an IPv6 route/neighbour lookup for me?" π¦
πΈ SYNOPSIS πΈ
struct nfp_tun_req_route_ipv6 {
__be32 ingress_port;
struct in6_addr ipv6_addr;
};
look at her. two members. no bloat. main character energy fr fr π
π MEMBERS π
ingress_portβ the ingress port of the packet that signalled this request. so like, which door did this packet come through πͺβ¨ipv6_addrβ the destination IPv6 address for the route. the actual address we're asking about, no cap π
π SEE ALSO π
like, go read these too, they're all in their own little friend group π«Ά:
- Kernel file
./drivers/net/ethernet/netronome/nfp/flower/tunnel_conf.c 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_ipv4(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)
no notes, just vibes. read them all, iykyk π
π§ cute sign-off π§
and that's the whole page! source file lives at ./drivers/net/ethernet/netrono... (truncation ate the rest, not me, blame the manpage renderer π) and this beauty was stamped October 2026. go forth and tunnel, bestie β struct nfp_...q_route_ipv6(9) out πβ¨π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms