# 'raddb/huntgroups' files.
preprocess
+ # If you intend to use CUI and you require that the Operator-Name
+ # be set for CUI generation and you want to generate CUI also
+ # for your local clients then uncomment the operator-name
+ # below and set the operator-name for your clients in clients.conf
+# operator-name
+ #
+ # If you want to generate CUI for some clients that do not
+ # send proper CUI requiests, then uncomment the
+ # cui below and set "add-cui = yes" for these clients in clients.conf
+# cui
+
#
# If you want to have a log of authentication requests,
# un-comment the following line, and the 'detail auth_log'
# Accounting. Log the accounting data.
#
accounting {
+ # Update accounting packet by adding the CUI attribute
+ # recorded from the corresponding Access-Accept
+ # use it only if your NAS boxes do not support CUI themselves
+# cui
#
# Create a 'detail'ed log of the packets.
# Note that accounting requests which are proxied
#
# wimax
+ # Create the CUI value and add the attribute to Access-Accept.
+ # Uncomment the line below if *returning* the CUI.
+# cui
+
# If there is a client certificate (EAP-TLS, sometimes PEAP
# and TTLS), then some attributes are filled out after the
# certificate verification has been performed. These fields
pre-proxy {
# attr_rewrite
+ # Before proxing the request add an Operator-Name attribute identifying
+ # if the operator-name is found for this client.
+ # No need to uncomment this if you have already enabled this in
+ # the authorize section.
+# operator-name
+
+ # The client requests the CUI by sending a CUI attribute
+ # containing one zero byte.
+ # Uncomment the line below if *requesting* the CUI.
+# cui
+
# Uncomment the following line if you want to change attributes
# as defined in the preproxy_users file.
# files