3 ## radiusd.conf -- FreeRADIUS server configuration file - @RADIUSD_VERSION_STRING@
5 ## http://www.freeradius.org/
9 ######################################################################
11 # Read "man radiusd" before editing this file. See the section
12 # titled DEBUGGING. It outlines a method where you can quickly
13 # obtain the configuration you want, without running into
16 # Run the server in debugging mode, and READ the output.
20 # We cannot emphasize this point strongly enough. The vast
21 # majority of problems can be solved by carefully reading the
22 # debugging output, which includes warnings about common issues,
23 # and suggestions for how they may be fixed.
25 # There may be a lot of output, but look carefully for words like:
26 # "warning", "error", "reject", or "failure". The messages there
27 # will usually be enough to guide you to a solution.
29 # If you are going to ask a question on the mailing list, then
30 # explain what you are trying to do, and include the output from
31 # debugging mode (radiusd -X). Failure to do so means that all
32 # of the responses to your question will be people telling you
33 # to "post the output of radiusd -X".
35 ######################################################################
37 # The location of other config files and logfiles are declared
40 # Also general configuration for modules can be done in this
41 # file, it is exported through the API to modules that ask for
44 # See "man radiusd.conf" for documentation on the format of this
45 # file. Note that the individual configuration items are NOT
46 # documented in that "man" page. They are only documented here,
49 # As of 2.0.0, FreeRADIUS supports a simple processing language
50 # in the "authorize", "authenticate", "accounting", etc. sections.
51 # See "man unlang" for details.
55 exec_prefix = @exec_prefix@
56 sysconfdir = @sysconfdir@
57 localstatedir = @localstatedir@
61 radacctdir = @radacctdir@
64 # name of the running server. See also the "-n" command-line option.
67 # Location of config and logfiles.
69 certdir = ${confdir}/certs
70 cadir = ${confdir}/certs
71 run_dir = ${localstatedir}/run/${name}
73 # Should likely be ${localstatedir}/lib/radiusd
77 # libdir: Where to find the rlm_* modules.
79 # This should be automatically set at configuration time.
81 # If the server builds and installs, but fails at execution time
82 # with an 'undefined symbol' error, then you can use the libdir
83 # directive to work around the problem.
85 # The cause is usually that a library has been installed on your
86 # system in a place where the dynamic linker CANNOT find it. When
87 # executing as root (or another user), your personal environment MAY
88 # be set up to allow the dynamic linker to find the library. When
89 # executing as a daemon, FreeRADIUS MAY NOT have the same
90 # personalized configuration.
92 # To work around the problem, find out which library contains that symbol,
93 # and add the directory containing that library to the end of 'libdir',
94 # with a colon separating the directory names. NO spaces are allowed.
96 # e.g. libdir = /usr/local/lib:/opt/package/lib
98 # You can also try setting the LD_LIBRARY_PATH environment variable
99 # in a script which starts the server.
101 # If that does not work, then you can re-configure and re-build the
102 # server to NOT use shared libraries, via:
104 # ./configure --disable-shared
110 # pidfile: Where to place the PID of the RADIUS server.
112 # The server may be signalled while it's running by using this
115 # This file is written when ONLY running in daemon mode.
117 # e.g.: kill -HUP `cat /var/run/radiusd/radiusd.pid`
119 pidfile = ${run_dir}/${name}.pid
121 # max_request_time: The maximum time (in seconds) to handle a request.
123 # Requests which take more time than this to process may be killed, and
124 # a REJECT message is returned.
126 # WARNING: If you notice that requests take a long time to be handled,
127 # then this MAY INDICATE a bug in the server, in one of the modules
128 # used to handle a request, OR in your local configuration.
130 # This problem is most often seen when using an SQL database. If it takes
131 # more than a second or two to receive an answer from the SQL database,
132 # then it probably means that you haven't indexed the database. See your
133 # SQL server documentation for more information.
135 # Useful range of values: 5 to 120
137 max_request_time = 30
139 # cleanup_delay: The time to wait (in seconds) before cleaning up
140 # a reply which was sent to the NAS.
142 # The RADIUS request is normally cached internally for a short period
143 # of time, after the reply is sent to the NAS. The reply packet may be
144 # lost in the network, and the NAS will not see it. The NAS will then
145 # re-send the request, and the server will respond quickly with the
148 # If this value is set too low, then duplicate requests from the NAS
149 # MAY NOT be detected, and will instead be handled as seperate requests.
151 # If this value is set too high, then the server will cache too many
152 # requests, and some new requests may get blocked. (See 'max_requests'.)
154 # Useful range of values: 2 to 10
158 # max_requests: The maximum number of requests which the server keeps
159 # track of. This should be 256 multiplied by the number of clients.
160 # e.g. With 4 clients, this number should be 1024.
162 # If this number is too low, then when the server becomes busy,
163 # it will not respond to any new requests, until the 'cleanup_delay'
164 # time has passed, and it has removed the old requests.
166 # If this number is set too high, then the server will use a bit more
167 # memory for no real benefit.
169 # If you aren't sure what it should be set to, it's better to set it
170 # too high than too low. Setting it to 1000 per client is probably
171 # the highest it should be.
173 # Useful range of values: 256 to infinity
177 # hostname_lookups: Log the names of clients or just their IP addresses
178 # e.g., www.freeradius.org (on) or 206.47.27.232 (off).
180 # The default is 'off' because it would be overall better for the net
181 # if people had to knowingly turn this feature on, since enabling it
182 # means that each client request will result in AT LEAST one lookup
183 # request to the nameserver. Enabling hostname_lookups will also
184 # mean that your server may stop randomly for 30 seconds from time
185 # to time, if the DNS requests take too long.
187 # Turning hostname lookups off also means that the server won't block
188 # for 30 seconds, if it sees an IP address which has no name associated
191 # allowed values: {no, yes}
193 hostname_lookups = no
196 # Logging section. The various "log_*" configuration items
197 # will eventually be moved here.
201 # Destination for log messages. This can be one of:
203 # files - log to "file", as defined below.
204 # syslog - to syslog (see also the "syslog_facility", below.
205 # stdout - standard output
206 # stderr - standard error.
208 # The command-line option "-X" over-rides this option, and forces
209 # logging to go to stdout.
214 # Highlight important messages sent to stderr and stdout.
216 # Option will be ignored (disabled) if output if TERM is not
217 # an xterm or output is not to a TTY.
222 # The logging messages for the server are appended to the
223 # tail of this file if destination == "files"
225 # If the server is running in debugging mode, this file is
228 file = ${logdir}/radius.log
231 # If this configuration parameter is set, then log messages for
232 # a *request* go to this file, rather than to radius.log.
234 # i.e. This is a log file per request, once the server has accepted
235 # the request as being from a valid client. Messages that are
236 # not associated with a request still go to radius.log.
238 # Not all log messages in the server core have been updated to use
239 # this new internal API. As a result, some messages will still
240 # go to radius.log. Please submit patches to fix this behavior.
242 # The file name is expanded dynamically. You should ONLY user
243 # server-side attributes for the filename (e.g. things you control).
244 # Using this feature MAY also slow down the server substantially,
245 # especially if you do thinks like SQL calls as part of the
246 # expansion of the filename.
248 # The name of the log file should use attributes that don't change
249 # over the lifetime of a request, such as User-Name,
250 # Virtual-Server or Packet-Src-IP-Address. Otherwise, the log
251 # messages will be distributed over multiple files.
253 # Logging can be enabled for an individual request by a special
254 # dynamic expansion macro: %{debug: 1}, where the debug level
255 # for this request is set to '1' (or 2, 3, etc.). e.g.
259 # Tmp-String-0 = "%{debug:1}"
263 # The attribute that the value is assigned to is unimportant,
264 # and should be a "throw-away" attribute with no side effects.
266 #requests = ${logdir}/radiusd-%{%{Virtual-Server}:-DEFAULT}-%Y%m%d.log
269 # Which syslog facility to use, if ${destination} == "syslog"
271 # The exact values permitted here are OS-dependent. You probably
272 # don't want to change this.
274 syslog_facility = daemon
276 # Log the full User-Name attribute, as it was found in the request.
278 # allowed values: {no, yes}
282 # Log authentication requests to the log file.
284 # allowed values: {no, yes}
288 # Log passwords with the authentication requests.
289 # auth_badpass - logs password if it's rejected
290 # auth_goodpass - logs password if it's correct
292 # allowed values: {no, yes}
297 # Log additional text at the end of the "Login OK" messages.
298 # for these to work, the "auth" and "auth_goopass" or "auth_badpass"
299 # configurations above have to be set to "yes".
301 # The strings below are dynamically expanded, which means that
302 # you can put anything you want in them. However, note that
303 # this expansion can be slow, and can negatively impact server
310 # The program to execute to do concurrency checks.
311 checkrad = ${sbindir}/checkrad
313 # SECURITY CONFIGURATION
315 # There may be multiple methods of attacking on the server. This
316 # section holds the configuration items which minimize the impact
320 # chroot: directory where the server does "chroot".
322 # The chroot is done very early in the process of starting
323 # the server. After the chroot has been performed it
324 # switches to the "user" listed below (which MUST be
325 # specified). If "group" is specified, it switches to that
326 # group, too. Any other groups listed for the specified
327 # "user" in "/etc/group" are also added as part of this
330 # The current working directory (chdir / cd) is left
331 # *outside* of the chroot until all of the modules have been
332 # initialized. This allows the "raddb" directory to be left
333 # outside of the chroot. Once the modules have been
334 # initialized, it does a "chdir" to ${logdir}. This means
335 # that it should be impossible to break out of the chroot.
337 # If you are worried about security issues related to this
338 # use of chdir, then simply ensure that the "raddb" directory
339 # is inside of the chroot, end be sure to do "cd raddb"
340 # BEFORE starting the server.
342 # If the server is statically linked, then the only files
343 # that have to exist in the chroot are ${run_dir} and
344 # ${logdir}. If you do the "cd raddb" as discussed above,
345 # then the "raddb" directory has to be inside of the chroot
348 # chroot = /path/to/chroot/directory
350 # user/group: The name (or #number) of the user/group to run radiusd as.
352 # If these are commented out, the server will run as the
353 # user/group that started it. In order to change to a
354 # different user/group, you MUST be root ( or have root
355 # privleges ) to start the server.
357 # We STRONGLY recommend that you run the server with as few
358 # permissions as possible. That is, if you're not using
359 # shadow passwords, the user and group items below should be
362 # NOTE that some kernels refuse to setgid(group) when the
363 # value of (unsigned)group is above 60000; don't use group
364 # "nobody" on these systems!
366 # On systems with shadow passwords, you might have to set
367 # 'group = shadow' for the server to be able to read the
368 # shadow password file. If you can authenticate users while
369 # in debug mode, but not in daemon mode, it may be that the
370 # debugging mode server is running as a user that can read
371 # the shadow info, and the user listed below can not.
373 # The server will also try to use "initgroups" to read
374 # /etc/groups. It will join all groups where "user" is a
375 # member. This can allow for some finer-grained access
381 # Core dumps are a bad thing. This should only be set to
382 # 'yes' if you're debugging a problem with the server.
384 # allowed values: {no, yes}
386 allow_core_dumps = no
389 # max_attributes: The maximum number of attributes
390 # permitted in a RADIUS packet. Packets which have MORE
391 # than this number of attributes in them will be dropped.
393 # If this number is set too low, then no RADIUS packets
396 # If this number is set too high, then an attacker may be
397 # able to send a small number of packets which will cause
398 # the server to use all available memory on the machine.
400 # Setting this number to 0 means "allow any number of attributes"
404 # reject_delay: When sending an Access-Reject, it can be
405 # delayed for a few seconds. This may help slow down a DoS
406 # attack. It also helps to slow down people trying to brute-force
407 # crack a users password.
409 # Setting this number to 0 means "send rejects immediately"
411 # If this number is set higher than 'cleanup_delay', then the
412 # rejects will be sent at 'cleanup_delay' time, when the request
413 # is deleted from the internal cache of requests.
415 # Useful ranges: 1 to 5
419 # status_server: Whether or not the server will respond
420 # to Status-Server requests.
422 # When sent a Status-Server message, the server responds with
423 # an Access-Accept or Accounting-Response packet.
425 # This is mainly useful for administrators who want to "ping"
426 # the server, without adding test users, or creating fake
427 # accounting packets.
429 # It's also useful when a NAS marks a RADIUS server "dead".
430 # The NAS can periodically "ping" the server with a Status-Server
431 # packet. If the server responds, it must be alive, and the
432 # NAS can start using it for real requests.
434 # See also raddb/sites-available/status
439 # PROXY CONFIGURATION
441 # proxy_requests: Turns proxying of RADIUS requests on or off.
443 # The server has proxying turned on by default. If your system is NOT
444 # set up to proxy requests to another server, then you can turn proxying
445 # off here. This will save a small amount of resources on the server.
447 # If you have proxying turned off, and your configuration files say
448 # to proxy a request, then an error message will be logged.
450 # To disable proxying, change the "yes" to "no", and comment the
453 # allowed values: {no, yes}
459 # CLIENTS CONFIGURATION
461 # Client configuration is defined in "clients.conf".
464 # The 'clients.conf' file contains all of the information from the old
465 # 'clients' and 'naslist' configuration files. We recommend that you
466 # do NOT use 'client's or 'naslist', although they are still
469 # Anything listed in 'clients.conf' will take precedence over the
470 # information from the old-style configuration files.
472 $INCLUDE clients.conf
475 # THREAD POOL CONFIGURATION
477 # The thread pool is a long-lived group of threads which
478 # take turns (round-robin) handling any incoming requests.
480 # You probably want to have a few spare threads around,
481 # so that high-load situations can be handled immediately. If you
482 # don't have any spare threads, then the request handling will
483 # be delayed while a new thread is created, and added to the pool.
485 # You probably don't want too many spare threads around,
486 # otherwise they'll be sitting there taking up resources, and
487 # not doing anything productive.
489 # The numbers given below should be adequate for most situations.
492 # Number of servers to start initially --- should be a reasonable
496 # Limit on the total number of servers running.
498 # If this limit is ever reached, clients will be LOCKED OUT, so it
499 # should NOT BE SET TOO LOW. It is intended mainly as a brake to
500 # keep a runaway server from taking the system with it as it spirals
503 # You may find that the server is regularly reaching the
504 # 'max_servers' number of threads, and that increasing
505 # 'max_servers' doesn't seem to make much difference.
507 # If this is the case, then the problem is MOST LIKELY that
508 # your back-end databases are taking too long to respond, and
509 # are preventing the server from responding in a timely manner.
511 # The solution is NOT do keep increasing the 'max_servers'
512 # value, but instead to fix the underlying cause of the
513 # problem: slow database, or 'hostname_lookups=yes'.
515 # For more information, see 'max_request_time', above.
519 # Server-pool size regulation. Rather than making you guess
520 # how many servers you need, FreeRADIUS dynamically adapts to
521 # the load it sees, that is, it tries to maintain enough
522 # servers to handle the current load, plus a few spare
523 # servers to handle transient load spikes.
525 # It does this by periodically checking how many servers are
526 # waiting for a request. If there are fewer than
527 # min_spare_servers, it creates a new spare. If there are
528 # more than max_spare_servers, some of the spares die off.
529 # The default values are probably OK for most sites.
531 min_spare_servers = 3
532 max_spare_servers = 10
534 # When the server receives a packet, it places it onto an
535 # internal queue, where the worker threads (configured above)
536 # pick it up for processing. The maximum size of that queue
539 # When the queue is full, any new packets will be silently
542 # The most common cause of the queue being full is that the
543 # server is dependent on a slow database, and it has received
544 # a large "spike" of traffic. When that happens, there is
545 # very little you can do other than make sure the server
546 # receives less traffic, or make sure that the database can
549 # max_queue_size = 65536
551 # There may be memory leaks or resource allocation problems with
552 # the server. If so, set this value to 300 or so, so that the
553 # resources will be cleaned up periodically.
555 # This should only be necessary if there are serious bugs in the
556 # server which have not yet been fixed.
558 # '0' is a special value meaning 'infinity', or 'the servers never
560 max_requests_per_server = 0
562 # Automatically limit the number of accounting requests.
563 # This configuration item tracks how many requests per second
564 # the server can handle. It does this by tracking the
565 # packets/s received by the server for processing, and
566 # comparing that to the packets/s handled by the child
569 # If the received PPS is larger than the processed PPS, *and*
570 # the queue is more than half full, then all new accounting
571 # requests are discarded. This lowers the received rate,
572 # and over time allows the server to "catch up" to the traffic.
577 # MODULE CONFIGURATION
579 # The names and configuration of each module is located in this section.
581 # After the modules are defined here, they may be referred to by name,
582 # in other sections of this configuration file.
586 # Each module has a configuration as follows:
588 # name [ instance ] {
589 # config_item = value
593 # The 'name' is used to load the 'rlm_name' library
594 # which implements the functionality of the module.
596 # The 'instance' is optional. To have two different instances
597 # of a module, it first must be referred to by 'name'.
598 # The different copies of the module are then created by
599 # inventing two 'instance' names, e.g. 'instance1' and 'instance2'
601 # The instance names can then be used in later configuration
602 # INSTEAD of the original 'name'. See the 'radutmp' configuration
607 # As of 3.0, modules are in mods-enabled/. Files matching
608 # the regex /[a-zA-Z0-9_.]+/ are loaded. The modules are
609 # initialized ONLY if they are referenced in a processing
610 # section, such as authorize, authenticate, accounting,
611 # pre/post-proxy, etc.
613 $INCLUDE ${confdir}/mods-enabled/
618 # This section orders the loading of the modules. Modules
619 # listed here will get loaded BEFORE the later sections like
620 # authorize, authenticate, etc. get examined.
622 # This section is not strictly needed. When a section like
623 # authorize refers to a module, it's automatically loaded and
624 # initialized. However, some modules may not be listed in any
625 # of the following sections, so they can be listed here.
627 # Also, listing modules here ensures that you have control over
628 # the order in which they are initalized. If one module needs
629 # something defined by another module, you can list them in order
630 # here, and ensure that the configuration will be OK.
634 # Allows the execution of external scripts.
635 # The entire command line (and output) must fit into 253 bytes.
637 # e.g. Framed-Pool = `%{exec:/bin/echo foo}`
641 # The expression module doesn't do authorization,
642 # authentication, or accounting. It only does dynamic
643 # translation, of the form:
645 # Session-Timeout = `%{expr:2 + 3}`
647 # So the module needs to be instantiated, but CANNOT be
648 # listed in any other section. See 'doc/rlm_expr' for
654 # The DHCP module currently just registers some DHCP related
655 # expansions, but will eventually contain all the code necessary
656 # for encoding and decoding DHCP packets.
662 # We add the counter module here so that it registers
663 # the check-name attribute before any module which sets
669 # subsections here can be thought of as "virtual" modules.
671 # e.g. If you have two redundant SQL servers, and you want to
672 # use them in the authorize and accounting sections, you could
673 # place a "redundant" block in each section, containing the
674 # exact same text. Or, you could uncomment the following
675 # lines, and list "redundant_sql" in the authorize and
676 # accounting sections.
678 #redundant redundant_sql {
684 ######################################################################
686 # Policies are virtual modules, similar to those defined in the
687 # "instantate" section above.
689 # Defining a policy in one of the policy.d files means that it can be
690 # referenced in multiple places as a *name*, rather than as a series of
691 # conditions to match, and actions to take.
693 # Policies are something like subroutines in a normal language, but
694 # they cannot be called recursively. They MUST be defined in order.
695 # If policy A calls policy B, then B MUST be defined before A.
697 ######################################################################
702 ######################################################################
704 # SNMP notificiations. Uncomment the following line to enable
705 # snmptraps. Note that you MUST also configure the full path
706 # to the "snmptrap" command in the "trigger.conf" file.
708 #$INCLUDE trigger.conf
710 ######################################################################
712 # Load virtual servers.
714 # This next $INCLUDE line loads files in the directory that
715 # match the regular expression: /[a-zA-Z0-9_.]+/
717 # It allows you to define new virtual servers simply by placing
718 # a file into the raddb/sites-enabled/ directory.
720 $INCLUDE sites-enabled/
722 ######################################################################
724 # All of the other configuration sections like "authorize {}",
725 # "authenticate {}", "accounting {}", have been moved to the
728 # raddb/sites-available/default
730 # This is the "default" virtual server that has the same
731 # configuration as in version 1.0.x and 1.1.x. The default
732 # installation enables this virtual server. You should
733 # edit it to create policies for your local site.
735 # For more documentation on virtual servers, see:
737 # raddb/sites-available/README
739 ######################################################################