ENUM BATADV_TT_CLIENT_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ enum batadv_tt_client_flags(9) ✨

okay bestie so this is a page from the Kernel API Manual and it's literally all about enum batadv_tt_client_flags β€” the TT client specific flags. tiny little bits, huge main character energy πŸ’…


πŸŽ€ NAME πŸŽ€

enum batadv_tt_client_flags β€” TT client specific flags, periodt.


πŸ¦‹ SYNOPSIS πŸ¦‹

enum batadv_tt_client_flags {
    BATADV_TT_CLIENT_DEL ,
    BATADV_TT_CLIENT_ROAM ,
    BATADV_TT_CLIENT_WIFI ,
    BATADV_TT_CLIENT_ISOLA ,
    BATADV_TT_CLIENT_NOPURGE ,
    BATADV_TT_CLIENT_NEW ,
    BATADV_TT_CLIENT_PENDING ,
    BATADV_TT_CLIENT_TEMP

};

so yeah, eight constants, all lowercase-screaming at you. icons only, no cap 🌈


🌸 Constants 🌸

  • BATADV_TT_CLIENT_DEL β€” the client has to be deleted from the table. it's giving eviction notice 😭
  • BATADV_TT_CLIENT_ROAM β€” the client roamed to/from another node, and the new update telling its new real location has not been received/sent yet. so it's in transit, lowkey lost 🧚
  • BATADV_TT_CLIENT_WIFI β€” this client is connected through a wifi interface. this info is used by the β€œAP Isolation” feature. yes it snitched, and yes it served 🫢
  • BATADV_TT_CLIENT_ISOLA β€” this client is considered β€œisolated”. this info is used by the Extended Isolation feature. alone but iconic πŸ’œ
  • BATADV_TT_CLIENT_NOPURGE β€” this client should never be removed from the table. it's protected, it's cherished, it stays πŸŽ€
  • BATADV_TT_CLIENT_NEW β€” this client has been added to the local table but has not been announced yet. brand new arrival, no introduction text 😳
  • BATADV_TT_CLIENT_PENDING β€” this client is marked for removal but it is kept in the table for one more originator interval for consistency purposes. it got a stay of execution fr fr πŸ’€
  • BATADV_TT_CLIENT_TEMP β€” this global client has been detected to be part of the network but no node has already announced it. found in the wild, undisclosed ✨

🌟 Description 🌟

okay so here's the tea on the bit layout β˜•

Bits from 0 to 7 are called remote flags because they are sent on the wire. like, actually transmitted, on the network, for everyone to see πŸ’«

Bits from 8 to 15 are called local flags because they are used for local computations only. just for us, private vibes πŸ™ˆ

Bits from 4 to 7 β€” a subset of remote flags β€” are ensured to be in sync with the other nodes in the network. to achieve this goal these flags are included in the TT CRC computation. so yeah, synchronisation is a whole commitment πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./include/uapi/linux/batman_adv.h enum, plus the whole friend group:

  • batadv_mcast_flags_priv(9)
  • enum batadv_gw_modes(9)
  • enum batadv_nl_attrs(9)
  • enum batadv_nl_commands(9)
  • enum batadv_tp_meter_reason(9)
  • enum batadv_ifla_attrs(9)

go read them, iykyk πŸ¦‹


ngl the source of this whole thing lives at ./include/uapi/linux, dated October 2026, and the page itself is enum batadv_tt_client_flags(9). that's the sign-off bestie, mwah πŸ’–βœ¨πŸŽ€
πŸ“¦ where this page comes from