2 ## radiusd.conf -- FreeRADIUS server configuration file.
4 ## http://www.freeradius.org/
8 # This is the radiusd.conf file used for testing EAP-SIM stuff.
12 # The location of other config files and
13 # logfiles are declared in this file
15 # Also general configuration for modules can be done
16 # in this file, it is exported through the API to
17 # modules that ask for it.
19 # The configuration variables defined here are of the form ${foo}
20 # They are local to this file, and do not change from request to
23 # The per-request variables are of the form %{Attribute-Name}, and
24 # are taken from the values of the attribute in the incoming
25 # request. See 'doc/variables.txt' for more information.
27 prefix = /elros/mcr/root
28 exec_prefix = ${prefix}
29 sysconfdir = ${prefix}/etc
30 localstatedir = ${prefix}/var
31 sbindir = ${exec_prefix}/sbin
32 logdir = ${localstatedir}/log/radius
33 raddbdir = ${sysconfdir}/raddb
34 radacctdir = ${logdir}/radacct
36 # Location of config and logfiles.
38 run_dir = ${localstatedir}/run/radiusd
41 # The logging messages for the server are appended to the
44 log_file = ${logdir}/radius.log
47 # libdir: Where to find the rlm_* modules.
49 # This should be automatically set at configuration time.
51 # If the server builds and installs, but fails at execution time
52 # with an 'undefined symbol' error, then you can use the libdir
53 # directive to work around the problem.
55 # The cause is usually that a library has been installed on your
56 # system in a place where the dynamic linker CANNOT find it. When
57 # executing as root (or another user), your personal environment MAY
58 # be set up to allow the dynamic linker to find the library. When
59 # executing as a daemon, FreeRADIUS MAY NOT have the same
60 # personalized configuration.
62 # To work around the problem, find out which library contains that symbol,
63 # and add the directory containing that library to the end of 'libdir',
64 # with a colon separating the directory names. NO spaces are allowed.
66 # e.g. libdir = /usr/local/lib:/opt/package/lib
68 # You can also try setting the LD_LIBRARY_PATH environment variable
69 # in a script which starts the server.
71 # If that does not work, then you can re-configure and re-build the
72 # server to NOT use shared libraries, via:
74 # ./configure --disable-shared
78 libdir = ${exec_prefix}/lib
80 # pidfile: Where to place the PID of the RADIUS server.
82 # The server may be signalled while it's running by using this
85 # This file is written when ONLY running in daemon mode.
87 # e.g.: kill -HUP `cat /var/run/radiusd/radiusd.pid`
89 pidfile = ${run_dir}/radiusd.pid
92 # user/group: The name (or #number) of the user/group to run radiusd as.
94 # If these are commented out, the server will run as the user/group
95 # that started it. In order to change to a different user/group, you
96 # MUST be root ( or have root privleges ) to start the server.
98 # We STRONGLY recommend that you run the server with as few permissions
99 # as possible. That is, if you're not using shadow passwords, the
100 # user and group items below should be set to 'nobody'.
102 # On SCO (ODT 3) use "user = nouser" and "group = nogroup".
104 # NOTE that some kernels refuse to setgid(group) when the value of
105 # (unsigned)group is above 60000; don't use group nobody on these systems!
107 # On systems with shadow passwords, you might have to set 'group = shadow'
108 # for the server to be able to read the shadow password file. If you can
109 # authenticate users while in debug mode, but not in daemon mode, it may be
110 # that the debugging mode server is running as a user that can read the
111 # shadow info, and the user listed below can not.
116 # max_request_time: The maximum time (in seconds) to handle a request.
118 # Requests which take more time than this to process may be killed, and
119 # a REJECT message is returned.
121 # WARNING: If you notice that requests take a long time to be handled,
122 # then this MAY INDICATE a bug in the server, in one of the modules
123 # used to handle a request, OR in your local configuration.
125 # This problem is most often seen when using an SQL database. If it takes
126 # more than a second or two to receive an answer from the SQL database,
127 # then it probably means that you haven't indexed the database. See your
128 # SQL server documentation for more information.
130 # Useful range of values: 5 to 120
132 max_request_time = 30
134 # cleanup_delay: The time to wait (in seconds) before cleaning up
135 # a reply which was sent to the NAS.
137 # The RADIUS request is normally cached internally for a short period
138 # of time, after the reply is sent to the NAS. The reply packet may be
139 # lost in the network, and the NAS will not see it. The NAS will then
140 # re-send the request, and the server will respond quickly with the
143 # If this value is set too low, then duplicate requests from the NAS
144 # MAY NOT be detected, and will instead be handled as seperate requests.
146 # If this value is set too high, then the server will cache too many
147 # requests, and some new requests may get blocked. (See 'max_requests'.)
149 # Useful range of values: 2 to 10
153 # max_requests: The maximum number of requests which the server keeps
154 # track of. This should be 256 multiplied by the number of clients.
155 # e.g. With 4 clients, this number should be 1024.
157 # If this number is too low, then when the server becomes busy,
158 # it will not respond to any new requests, until the 'cleanup_delay'
159 # time has passed, and it has removed the old requests.
161 # If this number is set too high, then the server will use a bit more
162 # memory for no real benefit.
164 # If you aren't sure what it should be set to, it's better to set it
165 # too high than too low. Setting it to 1000 per client is probably
166 # the highest it should be.
168 # Useful range of values: 256 to infinity
172 # bind_address: Make the server listen on a particular IP address, and
173 # send replies out from that address. This directive is most useful
174 # for machines with multiple IP addresses on one interface.
176 # It can either contain "*", or an IP address, or a fully qualified
177 # Internet domain name. The default is "*"
181 # port: Allows you to bind FreeRADIUS to a specific port.
183 # The default port that most NAS boxes use is 1645, which is historical.
184 # RFC 2138 defines 1812 to be the new port. Many new servers and
185 # NAS boxes use 1812, which can create interoperability problems.
187 # The port is defined here to be 0 so that the server will pick up
188 # the machine's local configuration for the radius port, as defined
191 # If you want to use the default RADIUS port as defined on your server,
192 # (usually through 'grep radius /etc/services') set this to 0 (zero).
194 # A port given on the command-line via '-p' over-rides this one.
198 # hostname_lookups: Log the names of clients or just their IP addresses
199 # e.g., www.freeradius.org (on) or 206.47.27.232 (off).
201 # The default is 'off' because it would be overall better for the net
202 # if people had to knowingly turn this feature on, since enabling it
203 # means that each client request will result in AT LEAST one lookup
204 # request to the nameserver. Enabling hostname_lookups will also
205 # mean that your server may stop randomly for 30 seconds from time
206 # to time, if the DNS requests take too long.
208 # Turning hostname lookups off also means that the server won't block
209 # for 30 seconds, if it sees an IP address which has no name associated
212 # allowed values: {no, yes}
214 hostname_lookups = no
216 # Core dumps are a bad thing. This should only be set to 'yes'
217 # if you're debugging a problem with the server.
219 # allowed values: {no, yes}
221 allow_core_dumps = yes
223 # Log the full User-Name attribute, as it was found in the request.
225 # allowed values: {no, yes}
227 log_stripped_names = no
229 # Log authentication requests to the log file.
231 # allowed values: {no, yes}
235 # Log passwords with the authentication requests.
236 # log_auth_badpass - logs password if it's rejected
237 # log_auth_goodpass - logs password if it's correct
239 # allowed values: {no, yes}
241 log_auth_badpass = no
242 log_auth_goodpass = no
244 # usercollide: Turn "username collision" code on and off. See the
245 # "doc/duplicate-users" file
249 # lower_user / lower_pass:
250 # Lower case the username/password "before" or "after"
251 # attempting to authenticate.
253 # If "before", the server will first modify the request and then try
254 # to auth the user. If "after", the server will first auth using the
255 # values provided by the user. If that fails it will reprocess the
256 # request after modifying it as you specify below.
258 # This is as close as we can get to case insensitivity. It is the
259 # admin's job to ensure that the username on the auth db side is
260 # *also* lowercase to make this work
262 # Default is 'no' (don't lowercase values)
263 # Valid values = "before" / "after" / "no"
268 # nospace_user / nospace_pass:
270 # Some users like to enter spaces in their username or password
271 # incorrectly. To save yourself the tech support call, you can
272 # eliminate those spaces here:
274 # Default is 'no' (don't remove spaces)
275 # Valid values = "before" / "after" / "no" (explanation above)
280 # The program to execute to do concurrency checks.
281 checkrad = ${sbindir}/checkrad
283 # SECURITY CONFIGURATION
285 # There may be multiple methods of attacking on the server. This
286 # section holds the configuration items which minimize the impact
291 # max_attributes: The maximum number of attributes
292 # permitted in a RADIUS packet. Packets which have MORE
293 # than this number of attributes in them will be dropped.
295 # If this number is set too low, then no RADIUS packets
298 # If this number is set too high, then an attacker may be
299 # able to send a small number of packets which will cause
300 # the server to use all available memory on the machine.
302 # Setting this number to 0 means "allow any number of attributes"
306 # reject_delay: When sending an Access-Reject, it can be
307 # delayed for a few seconds. This may help slow down a DoS
308 # attack. It also helps to slow down people trying to brute-force
309 # crack a users password.
311 # Setting this number to 0 means "send rejects immediately"
313 # If this number is set higher than 'cleanup_delay', then the
314 # rejects will be sent at 'cleanup_delay' time, when the request
315 # is deleted from the internal cache of requests.
317 # Useful ranges: 1 to 5
321 # status_server: Whether or not the server will respond
322 # to Status-Server requests.
324 # Normally this should be set to "no", because they're useless.
325 # See: http://www.freeradius.org/rfc/rfc2865.html#Keep-Alives
327 # However, certain NAS boxes may require them.
329 # When sent a Status-Server message, the server responds with
330 # and Access-Accept packet, containing a Reply-Message attribute,
331 # which is a string describing how long the server has been
337 # PROXY CONFIGURATION
339 # proxy_requests: Turns proxying of RADIUS requests on or off.
341 # The server has proxying turned on by default. If your system is NOT
342 # set up to proxy requests to another server, then you can turn proxying
343 # off here. This will save a small amount of resources on the server.
345 # If you have proxying turned off, and your configuration files say
346 # to proxy a request, then an error message will be logged.
348 # To disable proxying, change the "yes" to "no", and comment the
351 # allowed values: {no, yes}
354 $INCLUDE ${confdir}/proxy.conf
357 # CLIENTS CONFIGURATION
359 # Client configuration is defined in "clients.conf".
362 # The 'clients.conf' file contains all of the information from the old
363 # 'clients' and 'naslist' configuration files. We recommend that you
364 # do NOT use 'client's or 'naslist', although they are still
367 # Anything listed in 'clients.conf' will take precedence over the
368 # information from the old-style configuration files.
370 $INCLUDE ${confdir}/clients.conf
375 # Snmp configuration is only valid if SNMP support was enabled
378 # To enable SNMP querying of the server, set the value of the
379 # 'snmp' attribute to 'yes'
382 $INCLUDE ${confdir}/snmp.conf
385 # THREAD POOL CONFIGURATION
387 # The thread pool is a long-lived group of threads which
388 # take turns (round-robin) handling any incoming requests.
390 # You probably want to have a few spare threads around,
391 # so that high-load situations can be handled immediately. If you
392 # don't have any spare threads, then the request handling will
393 # be delayed while a new thread is created, and added to the pool.
395 # You probably don't want too many spare threads around,
396 # otherwise they'll be sitting there taking up resources, and
397 # not doing anything productive.
399 # The numbers given below should be adequate for most situations.
402 # Number of servers to start initially --- should be a reasonable
406 # Limit on the total number of servers running.
408 # If this limit is ever reached, clients will be LOCKED OUT, so it
409 # should NOT BE SET TOO LOW. It is intended mainly as a brake to
410 # keep a runaway server from taking the system with it as it spirals
413 # You may find that the server is regularly reaching the
414 # 'max_servers' number of threads, and that increasing
415 # 'max_servers' doesn't seem to make much difference.
417 # If this is the case, then the problem is MOST LIKELY that
418 # your back-end databases are taking too long to respond, and
419 # are preventing the server from responding in a timely manner.
421 # The solution is NOT do keep increasing the 'max_servers'
422 # value, but instead to fix the underlying cause of the
423 # problem: slow database, or 'hostname_lookups=yes'.
425 # For more information, see 'max_request_time', above.
429 # Server-pool size regulation. Rather than making you guess
430 # how many servers you need, FreeRADIUS dynamically adapts to
431 # the load it sees, that is, it tries to maintain enough
432 # servers to handle the current load, plus a few spare
433 # servers to handle transient load spikes.
435 # It does this by periodically checking how many servers are
436 # waiting for a request. If there are fewer than
437 # min_spare_servers, it creates a new spare. If there are
438 # more than max_spare_servers, some of the spares die off.
439 # The default values are probably OK for most sites.
441 min_spare_servers = 3
442 max_spare_servers = 10
444 # There may be memory leaks or resource allocation problems with
445 # the server. If so, set this value to 300 or so, so that the
446 # resources will be cleaned up periodically.
448 # This should only be necessary if there are serious bugs in the
449 # server which have not yet been fixed.
451 # '0' is a special value meaning 'infinity', or 'the servers never
453 max_requests_per_server = 0
456 # MODULE CONFIGURATION
458 # The names and configuration of each module is located in this section.
460 # After the modules are defined here, they may be referred to by name,
461 # in other sections of this configuration file.
465 # Each module has a configuration as follows:
467 # name [ instance ] {
468 # config_item = value
472 # The 'name' is used to load the 'rlm_name' library
473 # which implements the functionality of the module.
475 # The 'instance' is optional. To have two different instances
476 # of a module, it first must be referred to by 'name'.
477 # The different copies of the module are then created by
478 # inventing two 'instance' names, e.g. 'instance1' and 'instance2'
480 # The instance names can then be used in later configuration
481 # INSTEAD of the original 'name'. See the 'radutmp' configuration
482 # below for an example.
485 # PAP module to authenticate users based on their stored password
487 # Supports multiple encryption schemes
490 # md5: MD5 ecnryption
491 # sha1: SHA1 encryption.
494 encryption_scheme = crypt
499 # To authenticate requests containing a CHAP-Password attribute.
505 # Pluggable Authentication Modules
508 # http://www.kernel.org/pub/linux/libs/pam/index.html
512 # The name to use for PAM authentication.
513 # PAM looks in /etc/pam.d/${pam_auth_name}
514 # for it's configuration. See 'redhat/radiusd-pam'
515 # for a sample PAM configuration file.
517 # Note that any Pam-Auth attribute set in the 'authorize'
518 # section will over-ride this one.
523 # Unix /etc/passwd style authentication
527 # Cache /etc/passwd, /etc/shadow, and /etc/group
529 # The default is to NOT cache them.
531 # For FreeBSD, you do NOT want to enable the cache,
532 # as it's password lookups are done via a database, so
533 # set this value to 'no'.
535 # Some systems (e.g. RedHat Linux with pam_pwbd) can
536 # take *seconds* to check a password, from a passwd
537 # file containing 1000's of entries. For those systems,
538 # you should set the cache value to 'yes', and set
539 # the locations of the 'passwd', 'shadow', and 'group'
542 # allowed values: {no, yes}
545 # Reload the cache every 600 seconds (10mins). 0 to disable.
549 # Define the locations of the normal passwd, shadow, and
552 # 'shadow' is commented out by default, because not all
553 # systems have shadow passwords.
555 # To force the module to use the system password functions,
556 # instead of reading the files, leave the following entries
559 # This is required for some systems, like FreeBSD,
562 # passwd = /etc/passwd
563 # shadow = /etc/shadow
568 # Where the 'wtmp' file is located.
569 # This should be moved to it's own module soon.
571 # The only use for 'radlast'. If you don't use
572 # 'radlast', then you can comment out this item.
574 radwtmp = ${logdir}/radwtmp
577 # Extensible Authentication Protocol
579 # For all EAP related authentications
581 # Invoke the default supported EAP type when
582 # EAP-Identity response is received.
584 # The incoming EAP messages MAY NOT specify which EAP
585 # type they will be using, so it MUST be set here.
587 # For now, only one default EAP type may be used at a time.
589 default_eap_type = md5
591 # Default expiry time to clean the EAP list,
592 # It is maintained to correlate the
593 # EAP-response for each EAP-request sent.
596 # Supported EAP-types
605 # Cisco LEAP uses the MS-CHAP algorithm (but not
606 # the MS-CHAP attributes) to perform it's authentication.
608 # As a result, LEAP *requires* access to the plain-text
609 # User-Password, or the NT-Password attributes.
610 # 'System' authentication is impossible with LEAP.
615 ## EAP-TLS is highly experimental EAP-Type at the moment.
616 # Please give feedback on the mailing list.
618 # private_key_password = password
619 # private_key_file = /path/filename
621 # If Private key & Certificate are located in the
622 # same file, then private_key_file & certificate_file
623 # must contain the same file name.
624 # certificate_file = /path/filename
626 # Trusted Root CA list
627 #ca_file = /path/filename
629 # dh_file = /path/filename
630 #random_file = /path/filename
632 # This can never exceed MAX_RADIUS_LEN (4096)
633 # preferably half the MAX_RADIUS_LEN, to
634 # accomodate other attributes in RADIUS packet.
635 # On most APs the MAX packet length is configured
636 # between 1500 - 1600. In these cases, fragment
637 # size should be <= 1024.
639 # fragment_size = 1024
641 # include_length is a flag which is by default set to yes
642 # If set to yes, Total Length of the message is included
643 # in EVERY packet we send.
644 # If set to no, Total Length of the message is included
645 # ONLY in the First packet of a fragment series.
647 # include_length = yes
651 # Microsoft CHAP authentication
653 # This module supports MS-CHAP and MS-CHAPv2 authentication.
654 # It also enforces the SMB-Account-Ctrl attribute.
658 # As of 0.9, the mschap module does NOT support
659 # reading from /etc/smbpasswd.
661 # If you are using /etc/smbpasswd, see the 'passwd'
662 # module for an example of how to use /etc/smbpasswd
664 # authtype value, if present, will be used
665 # to overwrite (or add) Auth-Type during
666 # authorization. Normally should be MS-CHAP
669 # if use_mppe is not set to no mschap will
670 # add MS-CHAP-MPPE-Keys for MS-CHAPv1 and
671 # MS-MPPE-Recv-Key/MS-MPPE-Send-Key for MS-CHAPv2
674 # if mppe is enabled require_encryption makes
675 # encryption moderate
676 # require_encryption = yes
678 # require_strong always requires 128 bit key
680 # require_strong = yes
683 # Lightweight Directory Access Protocol (LDAP)
685 # This module definition allows you to use LDAP for
686 # authorization and authentication (Auth-Type := LDAP)
688 # See doc/rlm_ldap for description of configuration options
689 # and sample authorize{} and authenticate{} blocks
691 server = "ldap.your.domain"
692 # identity = "cn=admin,o=My Org,c=UA"
694 basedn = "o=My Org,c=UA"
695 filter = "(uid=%{Stripped-User-Name:-%{User-Name}})"
697 # set this to 'yes' to use TLS encrypted connections
698 # to the LDAP database by using the StartTLS extended
700 # The StartTLS operation is supposed to be used with normal
701 # ldap connections instead of using ldaps (port 636) connections
704 # default_profile = "cn=radprofile,ou=dialup,o=My Org,c=UA"
705 # profile_attribute = "radiusProfileDn"
706 access_attr = "dialupAccess"
708 # Mapping of RADIUS dictionary attributes to LDAP
709 # directory attributes.
710 dictionary_mapping = ${raddbdir}/ldap.attrmap
712 ldap_connections_number = 5
713 # password_header = "{clear}"
714 # password_attribute = userPassword
715 # groupname_attribute = cn
716 # groupmembership_filter = "(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))"
717 # groupmembership_attribute = radiusGroupName
721 # compare_check_items = yes
722 # access_attr_used_for_allow = yes
725 # passwd module allows to do authorization via any passwd-like
726 # file and to extract any attributes from these modules
729 # filename - path to filename
730 # format - format for filename record. This parameters
731 # correlates record in the passwd file and RADIUS
734 # Field marked as '*' is key field. That is, the parameter
735 # with this name from the request is used to search for
736 # the record from passwd file
737 # Attribute marked as '=' is added to reply_itmes instead
738 # of default configure_itmes
739 # Attribute marked as '~' is added to request_items
741 # Field marked as ',' may contain a comma separated list
743 # authtype - if record found this Auth-Type is used to authenticate
745 # hash_size - hashtable size. If 0 or not specified records are not
746 # stored in memory and file is red on every request.
747 # allow_multiple_keys - if few records for every key are allowed
748 # ignore_nislike - ignore NIS-related records
749 # delimiter - symbol to use as a field separator in passwd file,
750 # for format ':' symbol is always used. '\0', '\n' are
754 # An example configuration for using /etc/smbpasswd.
756 #passwd etc_smbpasswd {
757 # filename = /etc/smbpasswd
758 # format = "*User-Name::LM-Password:NT-Password:SMB-Account-CTRL-TEXT::"
761 # ignore_nislike = no
762 # allow_multiple_keys = no
765 # Similar configuration, for the /etc/group file. Adds a Group-Name
766 # attribute for every group that the user is member of.
769 # filename = /etc/group
770 # format = "=Group-Name:::*,User-Name"
772 # ignore_nislike = yes
773 # allow_multiple_keys = yes
777 # Realm module, for proxying.
779 # You can have multiple instances of the realm module to
780 # support multiple realm syntaxs at the same time. The
781 # search order is defined the order in the authorize and
782 # preacct blocks after the module config block.
784 # Two config options:
785 # format - must be 'prefix' or 'suffix'
786 # delimiter - must be a single character
790 # Using this entry, IPASS users have their realm set to "IPASS".
810 # Preprocess the incoming RADIUS request, before handing it off
813 # This module processes the 'huntgroups' and 'hints' files.
814 # In addition, it re-writes some weird attributes created
815 # by some NASes, and converts the attributes into a form which
816 # is a little more standard.
819 huntgroups = ${confdir}/huntgroups
820 hints = ${confdir}/hints
822 # This hack changes Ascend's wierd port numberings
823 # to standard 0-??? port numbers so that the "+" works
824 # for IP address assignments.
825 with_ascend_hack = no
826 ascend_channels_per_line = 23
828 # Windows NT machines often authenticate themselves as
831 # If this is set to 'yes', then the NT_DOMAIN portion
832 # of the user-name is silently discarded.
833 with_ntdomain_hack = no
835 # Specialix Jetstream 8500 24 port access server.
837 # If the user name is 10 characters or longer, a "/"
838 # and the excess characters after the 10th are
839 # appended to the user name.
841 # If you're not running that NAS, you don't need
843 with_specialix_jetstream_hack = no
845 # Cisco sends it's VSA attributes with the attribute
846 # name *again* in the string, like:
848 # H323-Attribute = "h323-attribute=value".
850 # If this configuration item is set to 'yes', then
851 # the redundant data in the the attribute text is stripped
852 # out. The result is:
854 # H323-Attribute = "value"
856 # If you're not running a Cisco NAS, you don't need
858 with_cisco_vsa_hack = no
861 # Livingston-style 'users' file
864 usersfile = ${confdir}/users
865 acctusersfile = ${confdir}/acct_users
867 # If you want to use the old Cistron 'users' file
868 # with FreeRADIUS, you should change the next line
869 # to 'compat = cistron'. You can the copy your 'users'
874 # Write a detailed log of all accounting records received.
877 # Note that we do NOT use NAS-IP-Address here, as
878 # that attribute MAY BE from the originating NAS, and
879 # NOT from the proxy which actually sent us the
880 # request. The Client-IP-Address attribute is ALWAYS
881 # the address of the client which sent us the
884 # The following line creates a new detail file for
885 # every radius client (by IP address or hostname).
886 # In addition, a new detail file is created every
887 # day, so that the detail file doesn't have to go
888 # through a 'log rotation'
890 # If your detail files are large, you may also want
891 # to add a ':%H' (see doc/variables.txt) to the end
892 # of it, to create a new detail file every hour, e.g.:
894 # ..../detail-%Y%m%d:%H
896 # This will create a new detail file for every hour.
898 detailfile = ${radacctdir}/%{Client-IP-Address}/detail-%Y%m%d
901 # The Unix-style permissions on the 'detail' file.
903 # The detail file often contains secret or private
904 # information about users. So by keeping the file
905 # permissions restrictive, we can prevent unwanted
906 # people from seeing that information.
910 # Include another file that has the SQL-related configuration.
911 # This is another file only because it tends to be big.
913 # The following configuration file is for use with MySQL.
915 # For Postgresql, use: ${confdir}/postgresql.conf
916 # For MS-SQL, use: ${confdir}/mssql.conf
917 # For Oracle, use: ${confdir}/oraclesql.conf
919 $INCLUDE ${confdir}/sql.conf
921 # Write a 'utmp' style file, of which users are currently
922 # logged in, and where they've logged in from.
924 # This file is used mainly for Simultaneous-Use checking,
925 # and also 'radwho', to see who's currently logged in.
928 # Where the file is stored. It's not a log file,
929 # so it doesn't need rotating.
931 filename = ${logdir}/radutmp
933 # The field in the packet to key on for the
934 # 'user' name, If you have other fields which you want
935 # to use to key on to control Simultaneous-Use,
936 # then you can use them here.
938 # Note, however, that the size of the field in the
939 # 'utmp' data structure is small, around 32
940 # characters, so that will limit the possible choices
943 username = %{User-Name}
945 # Whether or not we want to treat "user" the same
946 # as "USER", or "User". Some systems have problems
947 # with case sensitivity, so this should be set to
948 # 'no' to enable the comparisons of the key attribute
949 # to be case insensitive.
953 # Accounting information may be lost, so the user MAY
954 # have logged off of the NAS, but we haven't noticed.
955 # If so, we can verify this information with the NAS,
957 # If we want to believe the 'utmp' file, then this
958 # configuration entry can be set to 'no'.
962 # Set the file permissions, as the contents of this file
963 # are usually private.
969 # "Safe" radutmp - does not contain caller ID, so it can be
970 # world-readable, and radwho can work for normal users, without
971 # exposing any information that isn't already exposed by who(1).
973 # This is another 'instance' of the radutmp module, but it is given
974 # then name "sradutmp" to identify it later in the "accounting"
977 filename = ${logdir}/sradutmp
982 # attr_filter - filters the attributes received in replies from
983 # proxied servers, to make sure we send back to our RADIUS client
984 # only allowed attributes.
986 attrsfile = ${confdir}/attrs
990 # This module takes an attribute (count_attribute).
991 # It also takes a key, and creates a counter for each unique
992 # key. The count is incremented when accounting packets are
993 # received by the server. The value of the increment depends
994 # on the attribute type.
995 # If the attribute is Acct-Session-Time or of an integer type we add the
996 # value of the attribute. If it is anything else we increase the
999 # The 'reset' parameter defines when the counters are all reset to
1000 # zero. It can be hourly, daily, weekly, monthly or never.
1002 # hourly: Reset on 00:00 of every hour
1003 # daily: Reset on 00:00:00 every day
1004 # weekly: Reset on 00:00:00 on sunday
1005 # monthly: Reset on 00:00:00 of the first day of each month
1007 # It can also be user defined. It should be of the form:
1009 # h: hours, d: days, w: weeks, m: months
1010 # If the letter is ommited days will be assumed. In example:
1011 # reset = 10h (reset every 10 hours)
1012 # reset = 12 (reset every 12 days)
1015 # The check_name attribute defines an attribute which will be
1016 # registered by the counter module and can be used to set the
1017 # maximum allowed value for the counter after which the user
1021 # DEFAULT Max-Daily-Session := 36000
1024 # You should add the counter module in the instantiate
1025 # section so that it registers check_name before the files
1026 # module reads the users file.
1028 # If check_name is set and the user is to be rejected then we
1029 # send back a Reply-Message and we log a Failure-Message in
1031 # If the count attribute is Acct-Session-Time then on each login
1032 # we send back the remaining online time as a Session-Timeout attribute
1034 # The counter-name can also be used instead of using the check_name
1037 # DEFAULT Daily-Session-Time > 3600, Auth-Type = Reject
1038 # Reply-Message = "You've used up more than one hour today"
1040 # The allowed-servicetype attribute can be used to only take
1041 # into account specific sessions. For example if a user first
1042 # logs in through a login menu and then selects ppp there will
1043 # be two sessions. One for Login-User and one for Framed-User
1044 # service type. We only need to take into account the second one.
1046 # The module should be added in the instantiate, authorize and
1047 # accounting sections. Make sure that in the authorize
1048 # section it comes after any module which sets the
1049 # 'check_name' attribute.
1052 filename = ${raddbdir}/db.daily
1054 count_attribute = Acct-Session-Time
1056 counter_name = Daily-Session-Time
1057 check_name = Max-Daily-Session
1058 allowed_service_type = Framed-User
1062 # The "always" module is here for debugging purposes. Each
1063 # instance simply returns the same result, always, without
1078 # The 'expression' module currently has no configuration.
1083 # The 'digest' module currently has no configuration.
1085 # "Digest" authentication against a Cisco SIP server.
1086 # See 'doc/rfc/draft-sterman-aaa-sip-00.txt' for details
1087 # on performing digest authentication for Cisco SIP servers.
1093 # Execute external programs
1095 # The first example is useful only for 'xlat'. To use it,
1096 # put 'exec' into the 'instantiate' section. You can then
1097 # do dynamic translation of attributes like:
1099 # Attribute-Name = `{%exec:/path/to/program args}`
1101 # The value of the attribute will be replaced with the output
1102 # of the program which is executed. Due to RADIUS protocol
1103 # limitations, any output over 253 bytes will be ignored.
1105 # The RADIUS attributes from the user request will be placed
1106 # into environment variables of the executed program, as
1107 # described in 'doc/variables.txt'
1111 input_pairs = request
1115 # This is a more general example of the execute module.
1117 # If you wish to execute an external program in more than
1118 # one section (e.g. 'authorize', 'pre_proxy', etc), then it
1119 # is probably best to define a different instance of the
1120 # 'exec' module for every section.
1124 # Wait for the program to finish.
1126 # If we do NOT wait, then the program is "fire and
1127 # forget", and any output attributes from it are ignored.
1129 # If we are looking for the program to output
1130 # attributes, and want to add those attributes to the
1131 # request, then we MUST wait for the program to
1132 # finish, and therefore set 'wait=yes'
1134 # allowed values: {no, yes}
1138 # The name of the program to execute, and it's
1139 # arguments. Dynamic translation is done on this
1140 # field, so things like the following example will
1143 program = "/bin/echo %{User-Name}"
1146 # The attributes which are placed into the
1147 # environment variables for the program.
1149 # Allowed values are:
1151 # request attributes from the request
1152 # reply attributes from the reply
1153 # proxy-request attributes from the proxy request
1154 # proxy-reply attributes from the proxy reply
1156 # Note that some attributes may not exist at some
1157 # stages. e.g. There may be no proxy-reply
1158 # attributes if this module is used in the
1159 # 'authorize' section.
1161 input_pairs = request
1164 # Where to place the output attributes (if any) from
1165 # the executed program. The values allowed, and the
1166 # restrictions as to availability, are the same as
1167 # for the input_pairs.
1169 output_pairs = reply
1172 # When to execute the program. If the packet
1173 # type does NOT match what's listed here, then
1174 # the module does NOT execute the program.
1176 # For a list of allowed packet types, see
1177 # the 'dictionary' file, and look for VALUEs
1178 # of the Packet-Type attribute.
1180 # By default, the module executes on ANY packet.
1181 # Un-comment out the following line to tell the
1182 # module to execute only if an Access-Accept is
1183 # being sent to the NAS.
1185 #packet_type = Access-Accept
1188 # Do server side ip pool management. Should be added in post-auth and
1189 # accounting sections.
1191 # The module also requires the existance of the Pool-Name
1192 # attribute. That way the administrator can add the Pool-Name
1193 # attribute in the user profiles and use different pools
1194 # for different users. The Pool-Name attribute is a *check* item not
1198 # radiusd.conf: ippool students { [...] }
1199 # users file : DEFAULT Group == students, Pool-Name := "students"
1201 # ********* IF YOU CHANGE THE RANGE PARAMETERS YOU MUST THEN ERASE THE DB FILES *******
1205 # range-start,range-stop: The start and end ip
1206 # addresses for the ip pool
1207 range-start = 192.168.1.1
1208 range-stop = 192.168.3.254
1210 # netmask: The network mask used for the ip's
1211 netmask = 255.255.255.0
1213 # cache_size: The gdbm cache size for the db
1214 # files. Should be equal to the number of ip's
1215 # available in the ip pool
1218 # session-db: The main db file used to allocate ip's to clients
1219 session-db = ${raddbdir}/db.ippool
1221 # ip-index: Helper db index file used in multilink
1222 ip-index = ${raddbdir}/db.ipindex
1224 # override: Will this ippool override a Framed-IP-Address already set
1228 # ANSI X9.9 token support. Not included by default.
1229 # $INCLUDE ${confdir}/x99.conf
1235 # This section orders the loading of the modules. Modules
1236 # listed here will get loaded BEFORE the later sections like
1237 # authorize, authenticate, etc. get examined.
1239 # This section is not strictly needed. When a section like
1240 # authorize refers to a module, it's automatically loaded and
1241 # initialized. However, some modules may not be listed in any
1242 # of the following sections, so they can be listed here.
1244 # Also, listing modules here ensures that you have control over
1245 # the order in which they are initalized. If one module needs
1246 # something defined by another module, you can list them in order
1247 # here, and ensure that the configuration will be OK.
1251 # The expression module doesn't do authorization,
1252 # authentication, or accounting. It only does dynamic
1253 # translation, of the form:
1255 # Session-Timeout = `%{expr:2 + 3}`
1257 # So the module needs to be instantiated, but CANNOT be
1258 # listed in any other section. See 'doc/rlm_expr' for
1264 # We add the counter module here so that it registers
1265 # the check_name attribute before any module which sets
1270 # Authorization. First preprocess (hints and huntgroups files),
1271 # then realms, and finally look in the "users" file.
1273 # The order of the realm modules will determine the order that
1274 # we try to find a matching realm.
1276 # Make *sure* that 'preprocess' comes before any realm if you
1277 # need to setup hints for the remote radius server
1280 # The preprocess module takes care of sanitizing some bizarre
1281 # attributes in the request, and turning them into attributes
1282 # which are more standard.
1284 # It takes care of processing the 'raddb/hints' and the
1285 # 'raddb/huntgroups' files.
1287 # It also adds a Client-IP-Address attribute to the request.
1291 # The chap module will set 'Auth-Type := CHAP' if we are
1292 # handling a CHAP request and Auth-Type has not already been set
1298 # This module takes care of EAP-MD5, EAP-TLS, and EAP-LEAP
1303 # If you have a Cisco SIP server authenticating against
1304 # FreeRADIUS, uncomment the following line.
1308 # Look for IPASS style 'realm/', and if not found, look for
1309 # '@realm', and decide whether or not to proxy, based on
1315 # Read the 'users' file
1319 # If you are using /etc/smbpasswd, and are also doing
1320 # mschap authentication, the un-comment this line, and
1321 # configure the 'etc_smbpasswd' module, above.
1325 # If the users are logging in with an MS-CHAP-Challenge
1326 # attribute for authentication, the mschap module will find
1327 # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP'
1328 # to the request, which will cause the server to then use
1329 # the mschap module for authentication.
1333 # The ldap module will set Auth-Type to LDAP if it has not already been set
1341 # This section lists which modules are available for authentication.
1342 # Note that it does NOT mean 'try each module in order'. It means
1343 # that you have to have a module from the 'authorize' section add
1344 # a configuration attribute 'Auth-Type := FOO'. That authentication type
1345 # is then used to pick the appropriate module from the list below.
1347 # The default Auth-Type is Local. That is, whatever is not included inside
1348 # an authtype section will be called only if Auth-Type is set to Local.
1350 # So you should do the following:
1351 # - Set Auth-Type to an appropriate value in the authorize modules above.
1352 # For example, the chap module will set Auth-Type to CHAP, ldap to LDAP, etc.
1353 # - After that create corresponding authtype sections in the
1354 # authenticate section below and call the appropriate modules.
1357 # PAP authentication, when a back-end database listed
1358 # in the 'authorize' section supplies a password. The
1359 # password can be clear-text, or encrypted.
1365 # Most people want CHAP authentication
1366 # A back-end database listed in the 'authorize' section
1367 # MUST supply a CLEAR TEXT password. Encrypted passwords
1374 # MSCHAP authentication.
1380 # If you have a Cisco SIP server authenticating against
1381 # FreeRADIUS, uncomment the following line.
1385 # Pluggable Authentication Modules.
1389 # See 'man getpwent' for information on how the 'unix'
1390 # module checks the users password. Note that packets
1391 # containing CHAP-Password attributes CANNOT be authenticated
1392 # against /etc/passwd! See the FAQ for details.
1396 # Uncomment it if you want to use ldap for authentication
1403 # Allow EAP authentication.
1409 # Pre-accounting. Decide which accounting type to use.
1415 # Look for IPASS-style 'realm/', and if not found, look for
1416 # '@realm', and decide whether or not to proxy, based on
1419 # Accounting requests are generally proxied to the same
1420 # home server as authentication requests.
1425 # Read the 'acct_users' file
1430 # Accounting. Log the accounting data.
1434 # Ensure that we have a semi-unique identifier for every
1435 # request, and many NAS boxes are broken.
1439 # Create a 'detail'ed log of the packets.
1440 # Note that accounting requests which are proxied
1441 # are also logged in the detail file.
1448 # For Simultaneous-Use tracking.
1450 # Due to packet losses in the network, the data here
1451 # may be incorrect. There's little we can do about it.
1455 # Return an address to the IP Pool when we see a stop record.
1460 # Session database, used for checking Simultaneous-Use. Either the radutmp
1461 # or rlm_sql module can handle this.
1462 # The rlm_sql module is *much* faster
1469 # Post-Authentication
1470 # Once we KNOW that the user has been authenticated, there are
1471 # additional steps we can take.
1473 # Get an address from the IP Pool.
1478 # When the server decides to proxy a request to a home server,
1479 # the proxied request is first passed through the pre-proxy
1480 # stage. This stage can re-write the request, or decide to
1483 # Only a few modules currently have this method.
1489 # When the server receives a reply to a request it proxied
1490 # to a home server, the request may be massaged here, in the
1495 # If you are proxing LEAP, you MUST configure the EAP
1496 # module, and you MUST list it here, in the post-proxy
1499 # You MUST also use the 'nostrip' option in the 'realm'
1500 # configuration. Otherwise, the User-Name attribute
1501 # in the proxied request will not match the user name
1502 # hidden inside of the EAP packet, and the end server will
1503 # reject the EAP request.