radcli_avp_add_uint32(3)

📦 version 2.0.1, in arch rolling

💅 radcli_avp_add_uint32(3) — the Radius client library era 🎀

okay bestie, so this is a little function from the Radius client library manual, and honestly? it's giving "small but mighty." it appends a typed attribute to a list, and the types it handles are a very specific trio. let's get into it ✨

✨ NAME ✨

radcli_avp_add_uint32 — append an integer/IPv4-address/date-typed attribute. that's literally the whole job, and she does it well 🫶

🌸 SYNOPSIS 🌸

#include <radcli/>

int radcli_avp_add_uint32(
    radcli_avp_list        *list,
    const radcli_attr_def  *def,
    uint32_t                value
);

(yes, #include <radcli/> is exactly what the page says — we're copying it character for character, no cap 💅)

🦋 DESCRIPTION 🦋

so the DESCRIPTION section on this page is kinda shy and doesn't actually say anything extra 😭 — the real deets are chilling in PARAMETERS and RETURN VALUE right below, so scroll with me, iykyk.

💖 PARAMETERS 💖

  • list — the destination list. this is where the attribute goes to live. her new home 🏠
  • def — the attribute definition. and listen, it's picky: it must be RADCLI_TYPE_INTEGER, RADCLI_TYPE_IPADDR, or RADCLI_TYPE_DATE. those three. that's the vibe check, and if def doesn't pass it, we have problems 👑
  • value — the actual value being added. little heads up: an IPv4 address here is given in host byte order ⭐

🔥 RETURN VALUE 🔥

  • 0 — slay, success 🎉
  • -1 — it did NOT work out. this happens when def has none of the accepted types, or in the same situations as radcli_avp_add_bytes(). so yeah, check it, bestie, don't just assume 🙈

🌈 SEE ALSO 🌈

the whole friend group 🫶 — every single one of these:

and that's the page!! this one's from radcli, dated 2026-10-10 — so when you cite her, cite her correctly, bestie 💜 bye!! 🦋✨

📦 where this page comes from