radcli_dae_reply(3)

📦 version 2.0.1, in arch rolling

💅 radcli_dae_reply(3) — bestie edition 🎀

ok so this is a page from the Radius client library (yes, that radcli), and it's about answering DAE requests. buckle up, it's actually so clean ✨

✨ NAME ✨

radcli_dae_reply — answer a request with an ACK or NAK, selecting 41/42 or 44/45 from the request's own code, mirroring its Proxy-State attributes, and computing the Response Authenticator over the request's Authenticator. 🫶

like, it literally does four things at once and doesn't even brag about it. main character energy fr fr 👑

🌸 SYNOPSIS 🌸

#include <radcli/>

int radcli_dae_reply(
    radcli_dae_request  *req,
    int                  ack
);

💖 DESCRIPTION 💖

the whole vibe lives in the parameters and the return value, so let's get into it ⬇️

🦋 PARAMETERS 🦋

  • req — a request passed to a radcli_dae_handler, not yet replied to. lowkey important: not yet replied to. you get one shot at this one, bestie 💅
  • ack — non-zero for an ACK (Disconnect-ACK/CoA-ACK), zero for a bare NAK with no Error-Cause attribute. but listen — most callers rejecting a request should use radcli_dae_reply_error() instead, which also states why. so if you're about to send a naked NAK, just... don't 🙈 the error variant is right there and it explains itself iykyk

⭐ RETURN VALUE ⭐

  • 0 — once the reply is handed to the network. slay, it's out of your hands now 🕊️
  • -1 — on failure: req is NULL, it was already replied to, or the reply could not be sent. 💀
no cap, -1 is the "something went sideways" bucket — check whether you're double-replying before you go blaming the network 🙈

🌈 SEE ALSO 🌈

and that's the whole page, bestie 🍓 go forth and ACK responsibly 💜

radcli · 2026-10-10 · radcli_dae_reply(3) — mwah, xoxo 🧚‍♀️✨

📦 where this page comes from