radcli_avp...ytes_by_num(3)

💅 radcli_avp_add_bytes_by_num — NAME

okay so bestie, picture this: you're out here with a legacy numeric attribute ID (yes, the old-school kind, no judgement) and you just want to yeet some raw bytes into a list. That's literally the whole job of radcli_avp_add_bytes_by_num — look up an attribute by legacy numeric ID and append its bytes. iconic behaviour, no cap. ✨

---

🎀 SYNOPSIS

#include <radcli/>

int radcli_avp_add_bytes_by_num(
    radcli_avp_list   *list,
    const radcli_ctx  *ctx,
    uint32_t           attrid,
    uint32_t           vendor,
    const void        *value,
    size_t             len
);

---

🦋 DESCRIPTION

(this section is being its own main character — the details live in the parameters below 🫶)

---

🌸 PARAMETERS

• list — the destination list. it's giving "where the bytes are gonna live". 💖
• ctx — a context with a dictionary loaded. no dictionary, no lookup, you know how it is.
• attrid — the attribute ID. that's a PW_* constant, or a vendor type ID when vendor is non-zero. iykyk.
• vendor — the vendor PEN, or 0 for a standard attribute. zero means "no vendor energy, just vibes". ✨
• value — the bytes to copy in. it may be NULL only if len is 0. not me letting you skip that condition — it's real, fr fr. 🙈
• len — number of bytes at value. count 'em, bestie. 🔥

---

⭐ RETURN VALUE

0 on success. 🎉

-1 on failure — which happens when there's no such attribute, or for whatever reason radcli_avp_add_bytes() gives you. so if you see a -1, that's your plot twist. 💀

---

💜 SEE ALSO

her sisters, all equally iconic 👑

• radcli_avp_add_ip4_by_num(3)
• radcli_avp_add_ip4prefix_by_num(3)
• radcli_avp_add_ip6_by_num(3)
• radcli_avp_add_str_by_num(3)
• radcli_avp_add_uint32_by_num(3)
• radcli_avp_add_uint64_by_num(3)

---

okay that's the whole vibe check 💅 — this is from radcli, dated 2026-10-10, and that's the manual page, periodt. 🫶✨🌸