rc_acct_proxy(3)

πŸ“¦
version 1.5.2 Β· 4 versions
, in alpine 3.24, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

πŸ’– rc_acct_proxy β€” a lil page from the Radius client library πŸ’–

okay so bestie, we're in rc_acct_proxy(3) territory, and honestly? it's giving "short and sweet but don't sleep on it." pull up a chair, grab a strawberry πŸ“, and let's get into it.


✨ NAME ✨

rc_acct_proxy β€”

that's it. that's the name. no lil tagline, no subtitle, just the function name and a lonely dash, and we respect the mystery 🫢


🌸 SYNOPSIS 🌸

#include <radcli/radcli.h>

int rc_acct_proxy(
    rc_handle   *rh,
    VALUE_PAIR  *send
);

πŸ¦‹ DESCRIPTION πŸ¦‹

so what does it actually do, you ask? it builds an accounting request with the value_pairs you hand it at send. that's the whole vibe. you bring the pairs, it brings the request. πŸ’…


πŸŽ€ PARAMETERS πŸŽ€

  • rh β€” a handle to your parsed configuration. the whole setup lives in here, bestie.
  • send β€” a VALUE_PAIR array of values (e.g., PW_USER_NAME). this is the stuff you're sending out into the world ✨

πŸ‘‘ STRUCTURES πŸ‘‘

⚠️ okay important: avoid using this structure directly. use the rc_avpair_get_ functions instead, fr fr. no cap. πŸ™ˆ
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
};

look at all those fields. main character struct energy, honestly. πŸ’œ


πŸ”₯ RETURN VALUE πŸ”₯

  • OK_RC (0) on success β€” slay, it worked ✨
  • CHALLENGE_RC (3) when an Access-Challenge is received
  • negative on failure β€” as a return value, so keep an eye out πŸ‘€

🌈 SEE ALSO 🌈

the whole friend group, periodt:

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 that's the whole page, bestie. this one came from radcli, dated 2023-01-29, and it's literally rc_acct_proxy(3) β€” go build those accounting requests, you iconic lil network gremlin πŸ§šπŸ’–

πŸ“¦ where this page comes from