radcli_avp_add_ip4_by_num(3)

📦 version 2.0.1, in arch rolling

✨ NAME ✨

okay so bestie, this is radcli_avp_add_ip4_by_num — from the radcli Radius client library — and what it does is look up an IPv4-address-typed attribute by its legacy numeric ID and then append it. that's the whole vibe. 💅

🌸 SYNOPSIS 🌸

#include <radcli/>

int radcli_avp_add_ip4_by_num(
    radcli_avp_list   *list,
    const radcli_ctx  *ctx,
    uint32_t           attrid,
    uint32_t           vendor,
    struct in_addr     value
);

like, that's the whole incantation. no cap. 🫶

🦋 DESCRIPTION 🦋

so the description section is literally just the parameter breakdown, and honestly? iconic of it. let's get into it 👇

🎀 PARAMETERS 🎀

  • list — the destination list, queen. this is where the attribute is headed. ✨
  • ctx — a context with a dictionary loaded. yes, it needs the dictionary — that's the whole point of the lookup, iykyk. 📖
  • attrid — the attribute ID. this can be a PW_* constant, or a vendor type ID when vendor is non-zero. your call, bestie. 💜
  • vendor — the vendor PEN, or 0 for a standard attribute. zero means "no vendor, just a regular one". 🍓
  • value — the address, in the usual network byte order that struct in_addr carries. don't come at it with host byte order, I'm begging 😭

🔥 RETURN VALUE 🔥

  • 0 on success — slay, it worked 🎉
  • -1 on failure — either there's no such attribute, or it failed the same way radcli_avp_add_ip4() does. 💀
so yeah, -1 is doing double duty here. if things go sideways, that's where you'll see it. not me being dramatic, it's just what the page says 🫶

👑 SEE ALSO 👑

the whole by-num friend group, fr fr:

and that's the page!! 💖 brought to you by radcli, dated 2026-10-10, filed under radcli_avp_add_ip4_by_num(3) — go forth and append those IPv4 attributes, bestie. 🌈✨🎀

📦 where this page comes from