Dell PowerConnect W Clearpass 100 Software 3.9 Deployment Guide - Page 487

Example: Use the following as a conditional expression for an attribute. If the user's traffic in the past 24 hours exceeds 50 MB, the user is changed to the "Over-Quota" role. return GetUserTraffic(86400) > 50e6 && ChangeToRole("Over-Quota"); RADIUS Server Options These are the advanced server options that may be configured using the RADIUS Server Options text field. Where applicable, the default value for each configuration option is shown. The default value will be used if no other value is set in the RADIUS Server Options. Values for parameters may be quoted using double quotes; backslash escaping is supported within doublequoted strings. General Configuration Table 56 General Configuration Settings Value Description max_request_time = 30 cleanup_delay = 5 max_requests = 1024 bind_address = * listen.ipaddr = not set listen.port = not set The maximum time (in seconds) to handle a request. Requests which take more time than this to process may be killed, and a REJECT message is returned. The time to wait (in seconds) before cleaning up a reply which was sent to the NAS. The RADIUS request is normally cached internally for a short period of time, after the reply is sent to the NAS. The reply packet may be lost in the network, and the NAS will not see it. The NAS will then re-send the request, and the server will respond quickly with the cached reply. If this value is set too low, then duplicate requests from the NAS MAY NOT be detected, and will instead be handled as separate requests. If this value is set too high, then the server will cache too many requests, and some new requests may get blocked. (See max_requests, below) The useful range of values is 2 to 10 The maximum number of requests which the server keeps track of. This should be 256 multiplied by the number of clients, for example, with 4 clients, this number should be 1024. If this number is too low, then when the server becomes busy, it will not respond to any new requests, until the 'cleanup_delay' time has passed, and it has removed the old requests. If this number is set too high, then the server will use a bit more memory for no real benefit. If you aren't sure what it should be set to, it's better to set it too high than too low. Setting it to 1000 per client is probably the highest it should be. The useful range of values is 256 and higher. Make the server listen on a particular IP address, and send replies out from that address. This directive is most useful for machines with multiple IP addresses on one interface. It can either contain "*", or an IP address, or a fully qualified Internet domain name. By default, the server uses 'bind_address' to listen to all IP addresses on a machine, or just one IP. The 'port' configuration is used to select the authentication port used when listening on those addresses. If you want the server to listen on additional addresses, you can use the 'listen' section. The IP address on which to listen may be specified as a dotted-quad (1.2.3.4), hostname (radius.example.com) or as a wildcard (*). Port number on which to listen. Only applies if 'listen.ipaddr' has been set. Allowed values are an integer port number (1812) or 0 to look up the port in /etc/services. ClearPass Guest 3.9 | Deployment Guide Reference | 487