radcli_dae_new(3)

πŸ“¦ version 2.0.1, in arch rolling

✨ radcli_dae_new(3) β€” build a dynamic-authorization listener, but make it not-open-a-socket-yet ✨

Okay bestie, this is the Radius client library setup era: radcli_dae_new(3) validates your dae-* configuration and builds a dynamic-authorization listener. It opens no socket β€” that is radcli_dae_start()'s whole job, iykyk. 🫢


πŸ’– NAME πŸ’–

radcli_dae_new β€” validate dae-* configuration and build a dynamic-authorization listener. Opens no socket; see radcli_dae_start().


🌸 SYNOPSIS 🌸

#include <radcli/>

radcli_dae * radcli_dae_new(
    radcli_ctx  *ctx,
    unsigned     flags
);

πŸ¦‹ DESCRIPTION πŸ¦‹

Fails β€” as in returns NULL β€” unless dae-accept is "yes" or "udp". This is the safety lock so that a library upgrade never silently exposes a session-terminating channel in an application that did not opt in. No cap, that is a very good lock. πŸ”₯

When it is enabled, it also fails unless both dae-server and dae-secret are set, and unless every dae-server entry resolves and carries no network prefix.

At most one radcli_dae may be active on a given ctx at a time, since radcli_ctx_get_poll()/radcli_ctx_dispatch() operate on ctx and need a single descriptor to report. One listener per ctx, bestie β€” that is the vibe check. πŸ’…


πŸŽ€ PARAMETERS πŸŽ€

  • ctx β€” a configured context (rc_read_config()/rc_apply_config() already called).
  • flags β€” a bitwise OR of radcli_dae_flags, or 0 for the common case.

🌈 RETURN VALUE 🌈

Returns a new listener, or NULL on invalid configuration or an unknown flags bit. 😭


πŸ‘‘ SEE ALSO πŸ‘‘


That’s the whole glow-up: source/version radcli, dated 2026-10-10 β€” manual page radcli_dae_new(3), signing off. πŸ’…βœ¨

πŸ“¦ where this page comes from