rc_avpair_get_attr(3)
π rc_avpair_get_attr β from the Radius client library π
okay so bestie, welcome to rc_avpair_get_attr(3), one of the lil helper functions hanging out in the radcli family. she's from the Radius client library and she is, ngl, extremely straightforward. let's get into it π«Ά
β¨ NAME β¨
rc_avpair_get_attr β
and that's it. that's the whole description. the description slot is empty. she said "my name is enough" and honestly? main character energy. π
πΈ SYNOPSIS πΈ
#include <radcli/radcli.h>
void rc_avpair_get_attr(
VALUE_PAIR *vp,
unsigned *type,
unsigned *id
);
so you pull in <radcli/radcli.h> and then you call this with three things. that's the whole vibe check. β¨
π¦ DESCRIPTION π¦
lowkey the entire job description here is one sentence: this function gets the attribute ID and the type of the attribute value-pair you hand it.
that's it. no side quests. no hidden lore. she reads the pair, she tells you the type and the id. periodt. π
π PARAMETERS π
vpβ a pointer to aVALUE_PAIRstructure. yes, the one you want the deets from. hand her the pointer and she'll do the rest πtypeβ The attribute type, of typerc_attr_type. this is an out-param situation, she's gonna write the type back into it for you.idβ The attribute identifier, of typerc_attr_id. same deal, she fills this one in with the id.
π§ STRUCTURES π§
β οΈ bestie, listen to me very carefully: Avoid using this structure directly. Use the rc_avpair_get_ functions.
like fr fr, do not go poking around in there yourself. she's got helper functions for a reason. the struct is giving "look but don't touch" π
struct rc_value_pair {
char name[RC_NAME_LENGTH+1]; // attribute name if known.
uint64_t attribute; // attribute numeric value of type rc_attr_id including vendor; use VENDOR() and ATTRID() to separate.
rc_attr_type type; // attribute type.
uint32_t lvalue; // attribute value if type is PW_TYPE_INTEGER, PW_TYPE_DATE or PW_TYPE_IPADDR.
char strvalue[AUTH_STRING_LEN+1]; // contains attribute value in other cases.
struct rc_value_pair *next;
char pad[32]; // unused pad
};
okay breaking it down because I love you:
name[RC_NAME_LENGTH+1]β the attribute name, if it's known. the+1is for the null terminator, as always, we love a null terminator π₯°attributeβ the attribute numeric value, of typerc_attr_id, and yes it includes the vendor. useVENDOR()andATTRID()to separate them out. iykyk π«Άtypeβ the attribute type, of typerc_attr_type. hi again bestie.lvalueβ the attribute value if the type isPW_TYPE_INTEGER,PW_TYPE_DATEorPW_TYPE_IPADDR. those three. exactly those three.strvalue[AUTH_STRING_LEN+1]β contains the attribute value in other cases. so like, everything that isn't those three types up there βοΈnextβ pointer to the nextrc_value_pair. it's a linked list bestie, we're linking π¦pad[32]β unused pad. literally just vibes. she's sitting there taking up space and we respect her for it β¨
π SEE ALSO π
so many friends. an entire group chat, honestly:
radcli.h(3), rc_aaa(3), rc_aaa_ctx(3), rc_aaa_ctx_free(3), rc_aaa_ctx_get_secret(3), rc_aaa_ctx_get_vector(3), rc_aaa_ctx_server(3), rc_acct(3), rc_acct_proxy(3), rc_add_config(3), rc_apply_config(3), rc_auth(3), rc_auth_proxy(3), rc_avpair_add(3), rc_avpair_assign(3), rc_avpair_copy(3), rc_avpair_free(3), rc_avpair_gen(3), rc_avpair_get(3), rc_avpair_get_attr(3), rc_avpair_get_in6(3), rc_avpair_get_raw(3), rc_avpair_get_uint32(3), rc_avpair_insert(3), rc_avpair_log(3), rc_avpair_new(3), rc_avpair_next(3), rc_avpair_parse(3), rc_avpair_remove(3), rc_avpair_tostr(3), rc_buildreq(3), rc_check(3), rc_check_tls(3), rc_conf_int(3), rc_conf_srv(3), rc_conf_str(3), rc_config_free(3), rc_config_init(3), rc_destroy(3), rc_dict_addattr(3), rc_dict_addval(3), rc_dict_addvend(3), rc_dict_findattr(3), rc_dict_findval(3), rc_dict_findvend(3), rc_dict_free(3), rc_dict_getattr(3), rc_dict_getval(3), rc_dict_getvend(3), rc_find_server_addr(3), rc_get_socket_type(3), rc_get_srcaddr(3), rc_getport(3), rc_mksid(3), rc_new(3), rc_openlog(3), rc_own_hostname(3), rc_read_config(3), rc_read_dictionary(3), rc_read_dictionary_from_buffer(3), rc_send_server(3), rc_setdebug(3), rc_test_config(3), rc_tls_fd(3)
(and yeah, she's in her own SEE ALSO list. self-love. we stan π )
π and that's the page!! π
this one's from radcli, dated 2023-01-29, and it lives in the manual as rc_avpair_get_attr(3). go forth and get those attrs bestie, you're gonna slay ππβ¨
π¦ where this page comes from
- alpine 3.24: radcli-doc 1.4.0-r0 Β· BSD-2-Clause AND MIT
- epel 10: radcli-devel 1.5.2-3.el10_3 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 43: radcli-devel 1.4.0-5.fc43 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 43: radcli-devel 1.4.0-5.fc43 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 44: radcli-devel 1.4.0-6.fc44 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 44: radcli-devel 1.4.0-6.fc44 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 44: radcli-devel 1.5.2-3.fc44 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 44: radcli-devel 1.5.2-3.fc44 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- nixos 26.05: radcli 1.5.1
- nixpkgs unstable: radcli 1.5.2
- opensuse-leap 16.0: radcli-devel 1.4.0-bp160.1.11 Β· BSD-2-Clause AND MIT
- opensuse-leap 16.0: radcli-devel 1.4.0-bp160.1.11 Β· BSD-2-Clause AND MIT
- opensuse-leap 16.0: radcli-devel 1.4.0-bp160.1.11 Β· BSD-2-Clause AND MIT
- opensuse-leap 16.0: radcli-devel 1.4.0-bp160.1.11 Β· BSD-2-Clause AND MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms