Radiator Server Documentation — v10.34.2
Table of Contents

conditions

Each handler can be configured with an optional conditions clause. This clause is used to constraint which requests will be handled with it. If conditions are not defined, the handler will handle any request. A condition rule consists of a namespace attribute, comparison operator and one or more values to compare.

Handler conditions use the same syntax as policy conditions:

conditions <all | any | none> {
    <condition rules>
}

The condition block uses the all, any, or none matching strategy and can contain comparisons and nested condition blocks. For the matching strategies, nesting, evaluation order, and comparison operators, see Condition Blocks.

The following handler conditions select Access-Request messages that do not use PAP or CHAP:

conditions all {
    radius.request.code == radius.ACCESS_REQUEST;
    none {
        radius.request.method == radius.METHOD_PAP;
        radius.request.method == radius.METHOD_CHAP;
    }
}