HI - Have a look at “goodies/hooks.txt” - there are lots of examples.
For anything else you will need to look at the source code. The manual also details how hooks are called (“doc/ref.pdf”). regards Hugh > On 16 Sep 2019, at 15:29, Dubravko Penezic <[email protected]> wrote: > > Hi Hugh, > > thanks for respond, but it isnt question what RADIUS service need to > respond upon RADIUS request which is describe in RFC indeed. > > My question is relate to Perl code which is execute on any Hook in > RADIATOR. In many examples Hook code finish just with return in some > return some value, or two. > > To have correct Hook code i would like to learn what is correct way to > finish Hook Perl code, and do some short cut if is possible. > > Regards, > Dubravko > > On 9/14/19 1:28 AM, Hugh Irvine wrote: >> >> Hi again - >> >> The RADIUS protocol defines a number of different responses that a server >> must implement. >> >> If the user credentials pass verification, then respond with Accept. >> >> If the user credentials fail verification, then respond with Reject. >> >> If the user credentials can’t be verified, as in the case of an SQL database >> failure or unreachable, then don’t respond at all - ie Ignore. >> >> RADIUS clients are typically configured with a primary and secondary RADIUS >> server target, and will fail over if no response is received. >> >> Have a look at the RADIUS RFC’s for details. >> >> regards >> >> Hugh >> >> >>> On 13 Sep 2019, at 17:11, Dubravko Penezic <[email protected]> wrote: >>> >>> Hi, >>> >>> i wonder what exactly did follow line in Perl code when hook is called : >>> >>> return ($main::IGNORE, 'Database failure'); >>> >>> I didnt found what may be return codes, and how they control execution >>> process. >>> >>> Regards, >>> Dubravko >>> _______________________________________________ >>> radiator mailing list >>> [email protected] >>> https://lists.open.com.au/mailman/listinfo/radiator >> >> >> -- >> >> Hugh Irvine >> [email protected] >> >> Radiator: the most portable, flexible and configurable RADIUS server >> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, >> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, >> TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, >> DIAMETER, SIM, etc. >> Full source on Unix, Linux, Windows, macOS, Solaris, VMS, NetWare etc. >> > -- Hugh Irvine [email protected] Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER, SIM, etc. Full source on Unix, Linux, Windows, macOS, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list [email protected] https://lists.open.com.au/mailman/listinfo/radiator
