radcli_dae_reply_error(3)

πŸ“¦ version 2.0.1, in arch rolling

🌸 NAME 🌸

radcli_dae_reply_error(3) β€” Answer a request with a NAK carrying the given Error-Cause. ✨

okay bestie, welcome to radcli_dae_reply_error(3), fresh out of the Radius client library. This is the little reply-error icon we’re talking about today. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <radcli/>

int radcli_dae_reply_error(
    radcli_dae_request  *req,
    uint32_t             error_cause
);

πŸŽ€ DESCRIPTION πŸŽ€

Okay so picture this: this is the function that answers a request with a NAK carrying the given Error-Cause. Short, iconic, to the point. No cap, that’s the vibe. πŸ’–


🌈 PARAMETERS 🌈

  • req β€” a request passed to a radcli_dae_handler, not yet replied to. She’s still waiting for her moment, okay? 🫢
  • error_cause β€” a radcli_error_cause value (e.g. RADCLI_ERROR_SESSION_CONTEXT_NOT_FOUND), encoded as attribute 101. Yes, attribute 101, put some respect on it. ⭐

πŸ”₯ RETURN VALUE πŸ”₯

  • 0 β€” once the reply is handed to the network. slay, delivered. βœ…
  • -1 β€” on failure (req is NULL, already replied to, or the reply could not be sent). oof, bestie, something went sideways. 😭

πŸ‘‘ SEE ALSO πŸ‘‘


that’s the whole page, bestie β€” brought to you by radcli, dated 2026-10-10, and filed under radcli_dae_reply_error(3). πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from