ENUM BATADV_TT_CLIENT_FLAGS(9)
β¨ 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 isenum batadv_tt_client_flags(9). that's the sign-off bestie, mwah πβ¨π
π¦ 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