STRUCT NFP_TUN_ACTIVE_TUNS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct nfp_tun_active_tuns(9) β€” the kernel API manual, but make it cute πŸŽ€

okay bestie, so this is a page from the Kernel API Manual, and it's all about struct nfp_tun_active_tuns β€” like, the literal definition of it. no cap. it's the struct, the members, the whole vibe. let's go ✨


🌸 NAME 🌸

struct nfp_tun_active_tuns β€” lowkey the periodic message of active tunnels. that's the whole gig, she's a message, she's periodic, she's about tunnels. iconic πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

here's the shape of her, exactly as she is, do not touch:

struct nfp_tun_active_tuns {
    __be32 seq;
    __be32 count;
    __be32 flags;
    struct route_ip_info {
      __be32 ipv4;
      __be32 egress_port;
      __be32 extra[2];
    } tun_info[];
 };

ok so she's got a struct route_ip_info nested inside her, and tun_info[] is a lil flexible array situation at the end. literally main character energy 🌈


πŸ‘‘ Members πŸ‘‘

okay this is the part where we meet the whole friend group 🫢

  • seq β€” the sequence number of the message. it's giving "which one is this, in the order of things" πŸ’«
  • count β€” the number of tunnels report in message. yep, she's keeping score of how many tunnels are showing up to the function πŸ“Š
  • flags β€” the options part of the request. lil toggle-y bits, no further deets given, she's mysterious like that πŸ™ˆ
  • tun_info β€” the tunnels that have sent traffic in reported period. the actual active girlies!! the ones who showed up and did the work πŸ”₯

and then tun_info has her own little inner circle, bestie, look:

🧚 tun_info's inner circle 🧚

  • tun_info.ipv4 β€” the dest IPv4 address of active route. where the active route is headed, v4 flavour πŸ’œ
  • tun_info.egress_port β€” the port the encapsulated packet egressed. like, the exact door the packet left through πŸšͺ✨
  • tun_info.extra β€” reserved for future use. don't touch her, she's resting, she's for later πŸ’€

⭐ SEE ALSO ⭐

so if you wanna go deeper (and you should), go look at the kernel file:

Kernel file ./drivers/net/ethernet/netronome/nfp/flower/tunnel_conf.c

and these absolute icons of structs, all sitting together in the same orbit πŸͺ:

  • struct nfp_tun_pre_tun_rule(9)
  • struct nfp_tun_active_tuns_v6(9)
  • struct nfp_tun_req_route_ipv4(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)
ngl that's a long guest list but everybody's invited, that's just how we do it πŸ’€πŸ’–

and that's the whole page bestie, 10/10, no notes πŸ“

sign-off time: this one comes from ./drivers/net/ethernet/netrono... and she's dated October 2026, and she's out here living her life as struct nfp_tun_active_tuns(9). slay, periodt, bye πŸ’…πŸŒΈ

πŸ“¦ where this page comes from