When TriggerFailure is set, timed out requests, TCAP Abort primitive, MAP errors, and broken messages trigger a failure indication to upper layers, such as EAP-AKA, when the received message can be mapped to a sent message. Enabling TriggerFailure allows Radiator to reject authentication attempts instead of ignoring them. TriggerFailure is not set by default.

By default errors and time outs are logged and otherwise ignored. When the client has more than one RADIUS server configured, it can switch to a secondary server if the current server does not answer. This helps recovering from transient connectivity and other problems.

Here is an example of using TriggerFailure:

# We don't want cause time outs to RADIUS client
TriggerFailure