STRUCT FLOW_DISSECTOR_KEY_ETH_ADDRS(9)
π struct flow_dissector_key_eth_addrs(9) π
okay so first things first, bestie β this is a page from the Kernel API Manual, and the struct in question is struct flow_dissector_key_eth_addrs. That's the whole NAME entry, fr fr. No cute little one-liner description, no nothing. Just the struct name and a dash. She said "my name is enough" and honestly? main character energy. π
β¨ SYNOPSIS β¨
here's the whole thing, and yes it is this small, don't come for her:
struct flow_dissector_key_eth_addrs {
unsigned char dst[ETH_ALEN];
unsigned char src[ETH_ALEN];
};
look at that. two fields. two little unsigned char arrays, both sized ETH_ALEN, one for each direction of the conversation. she's compact, she's efficient, she's not doing too much. we love a low-effort icon. π
π Members π
dstβ the destination Ethernet address. where the packet is headed, the whole point of the journey, the final boss of the Ethernet frame. π―srcβ the source Ethernet address. where it came from, the origin story, the "no bc this is literally me" of the frame. πΈ
that's it. that's the members section. two entries. short and sweet and I'm obsessed. π«Ά
π¦ SEE ALSO π¦
okay so this is where things get a little unhinged (affectionate) because the see-also list is long and I need you to stay with me. the kernel file lives at ./include/net/flow_dissector.h β that's the struct's home base, her address, iykyk β and then she's linking arms with basically the entire flow dissector friend group:
struct flow_dissector_key_control(9)struct flow_dissector_key_basic(9)struct flow_dissector_key_enc_opts(9)struct flow_dissector_key_ipv4_addrs(9)struct flow_dissector_key_ipv6_addrs(9)struct flow_dissector_key_tipc(9)struct flow_dissector_key_addrs(9)struct flow_dissector_key_arp(9)struct flow_dissector_key_ports(9)struct flow_dissector_key_ports_range(9)struct flow_dissector_key_icmp(9)struct flow_dissector_key_tcp(9)struct flow_dissector_key_ip(9)struct flow_dissector_key_meta(9)struct flow_dissector_key_ct(9)struct flow_dissector_key_hash(9)struct flow_dissector_key_num_of_vlans(9)struct flow_dissector_key_pppoe(9)struct flow_dissector_key_l2tpv3(9)struct flow_dissector_key_ipsec(9)struct flow_dissector_key_cfm(9)
twenty-one friends and not one of them is a filler member of the group chat. that's called having taste. π
ngl bestie, if you're reading this page you probably don't need the lore β you just need to know thatdstcomes first andsrccomes second in the struct. do with that what you will. π
and that's the whole page!! no more lore, no more flags, no exit statuses, nothing dramatic β just two MAC-sized arrays and a whole lot of link love. the source is ./include/net, dated October 2026, and the page itself is struct flow...ey_eth_addrs(9) (yes the title got cropped, she's mysterious like that π). mwah, go read the flow dissector header, and remember: every Ethernet frame has a source and a destination, just like every group chat has a sender and a very confused recipient. πβ¨π§π
π¦ 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