radcli_avp_add_uint64(3)
π radcli_avp_add_uint64(3) π
okay bestie, welcome to the radcli manual, section 3, and honestly? this little function is lowkey iconic. it appends attributes, it's giving "small but does the most" energy, and by the end of this page you're gonna be obsessed. let's go π«Ά
β¨ NAME β¨
radcli_avp_add_uint64 β append a 64-bit integer-typed attribute, or an ifid-typed one. both. it's versatile like that π
πΈ SYNOPSIS πΈ
#include <radcli/>
int radcli_avp_add_uint64(
radcli_avp_list *list,
const radcli_attr_def *def,
uint64_t value
);
π¦ DESCRIPTION π¦
so the DESCRIPTION section itself is literally just vibes β there's no extra prose here, no filler, nothing. the entire personality of this function lives down in PARAMETERS and RETURN VALUE, so scroll a tiny bit and get the tea π
π PARAMETERS π
listβ the destination list, aka where your little attribute is gonna live. it's the main character's home πdefβ the attribute itself, and here's the catch: it must beRADCLI_TYPE_INTEGER64orRADCLI_TYPE_IFID. that's it, those are the only two accepted types, no cap.
and like, a little context on the ifid situation because it's genuinely fascinating: RADCLI_TYPE_IFID is RFC 8044 SS3.7's "ifid" data type β an opaque 8-octet value. but on the wire it's identical in shape to RADCLI_TYPE_INTEGER64, so instead of getting its own whole setter function, it just shares this one. efficiency! we love to see it β¨
valueβ the value, obviously π and forRADCLI_TYPE_IFIDspecifically, this is the raw 8 octets read as a big-endianuint64_t. big-endian, bestie. remember it.
π₯ RETURN VALUE π₯
0on success β slay π-1on failure β and that happens whendefhas neither of the accepted types, or for the same reasons asradcli_avp_add_bytes()would fail. yeah. that one. π
π SEE ALSO π
the whole extended fam, every single one, no skips:
radcli_avp_add_bytes(3)radcli_avp_add_bytes_by_num(3)radcli_avp_add_gigawords64(3)radcli_avp_add_gigawords64_by_num(3)radcli_avp_add_ip4(3)radcli_avp_add_ip4_by_num(3)radcli_avp_add_ip4prefix(3)radcli_avp_add_ip4prefix_by_num(3)radcli_avp_add_ip6(3)radcli_avp_add_ip6_by_num(3)radcli_avp_add_str(3)radcli_avp_add_str_by_num(3)radcli_avp_add_uint32(3)radcli_avp_add_uint32_by_num(3)radcli_avp_add_uint64_by_num(3)radcli_avp_add_username(3)radcli_avp_concat_str(3)radcli_avp_concat_str_by_num(3)radcli_avp_def(3)radcli_avp_get(3)radcli_avp_get_by_num(3)radcli_avp_get_bytes(3)radcli_avp_get_bytes_by_num(3)radcli_avp_get_cstr(3)radcli_avp_get_cstr_by_num(3)radcli_avp_get_gigawords64(3)radcli_avp_get_gigawords64_by_num(3)radcli_avp_get_ip4prefix(3)radcli_avp_get_ip4prefix_by_num(3)radcli_avp_get_ip6(3)radcli_avp_get_ip6_by_num(3)radcli_avp_get_uint32(3)radcli_avp_get_uint32_by_num(3)radcli_avp_get_uint64(3)radcli_avp_get_uint64_by_num(3)radcli_avp_iter_next(3)radcli_avp_list_error(3)radcli_avp_list_free(3)radcli_avp_list_iter(3)radcli_avp_list_new(3)
ok that's the whole page, you ate that ngl π go forth and append those 64-bit integers (and ifids, big-endian, raw 8 octets, you know the drill) π§
mwah π this page came from the radcli fam and is dated 2026-10-10 β catch you on the next one, bestie! πβ
π¦ where this page comes from
- arch rolling: radcli 2.0.1-1 Β· BSD
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms