Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ######################################################################
- #
- # As of 2.0.0, FreeRADIUS supports virtual hosts using the
- # "server" section, and configuration directives.
- #
- # Virtual hosts should be put into the "sites-available"
- # directory. Soft links should be created in the "sites-enabled"
- # directory to these files. This is done in a normal installation.
- #
- # If you are using 802.1X (EAP) authentication, please see also
- # the "inner-tunnel" virtual server. You wll likely have to edit
- # that, too, for authentication to work.
- #
- # $Id$
- #
- ######################################################################
- #
- # Read "man radiusd" before editing this file. See the section
- # titled DEBUGGING. It outlines a method where you can quickly
- # obtain the configuration you want, without running into
- # trouble. See also "man unlang", which documents the format
- # of this file.
- #
- # This configuration is designed to work in the widest possible
- # set of circumstances, with the widest possible number of
- # authentication methods. This means that in general, you should
- # need to make very few changes to this file.
- #
- # The best way to configure the server for your local system
- # is to CAREFULLY edit this file. Most attempts to make large
- # edits to this file will BREAK THE SERVER. Any edits should
- # be small, and tested by running the server with "radiusd -X".
- # Once the edits have been verified to work, save a copy of these
- # configuration files somewhere. (e.g. as a "tar" file). Then,
- # make more edits, and test, as above.
- #
- # There are many "commented out" references to modules such
- # as ldap, sql, etc. These references serve as place-holders.
- # If you need the functionality of that module, then configure
- # it in radiusd.conf, and un-comment the references to it in
- # this file. In most cases, those small changes will result
- # in the server being able to connect to the DB, and to
- # authenticate users.
- #
- ######################################################################
- #
- # In 1.x, the "authorize", etc. sections were global in
- # radiusd.conf. As of 2.0, they SHOULD be in a server section.
- #
- # The server section with no virtual server name is the "default"
- # section. It is used when no server name is specified.
- #
- # We don't indent the rest of this file, because doing so
- # would make it harder to read.
- #
- # Authorization. First preprocess (hints and huntgroups files),
- # then realms, and finally look in the "users" file.
- #
- # Any changes made here should also be made to the "inner-tunnel"
- # virtual server.
- #
- # The order of the realm modules will determine the order that
- # we try to find a matching realm.
- #
- # Make *sure* that 'preprocess' comes before any realm if you
- # need to setup hints for the remote radius server
- authorize {
- #
- # Security settings. Take a User-Name, and do some simple
- # checks on it, for spaces and other invalid characters. If
- # it looks like the user is trying to play games, reject it.
- #
- # This should probably be enabled by default.
- #
- # See policy.conf for the definition of the filter_username policy.
- #
- # filter_username
- #
- # The preprocess module takes care of sanitizing some bizarre
- # attributes in the request, and turning them into attributes
- # which are more standard.
- #
- # It takes care of processing the 'raddb/hints' and the
- # 'raddb/huntgroups' files.
- preprocess
- #
- # If you want to have a log of authentication requests,
- # un-comment the following line, and the 'detail auth_log'
- # section, above.
- # auth_log
- #
- # The chap module will set 'Auth-Type := CHAP' if we are
- # handling a CHAP request and Auth-Type has not already been set
- chap
- #
- # If the users are logging in with an MS-CHAP-Challenge
- # attribute for authentication, the mschap module will find
- # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP'
- # to the request, which will cause the server to then use
- # the mschap module for authentication.
- mschap
- #
- # If you have a Cisco SIP server authenticating against
- # FreeRADIUS, uncomment the following line, and the 'digest'
- # line in the 'authenticate' section.
- digest
- #
- # The WiMAX specification says that the Calling-Station-Id
- # is 6 octets of the MAC. This definition conflicts with
- # RFC 3580, and all common RADIUS practices. Un-commenting
- # the "wimax" module here means that it will fix the
- # Calling-Station-Id attribute to the normal format as
- # specified in RFC 3580 Section 3.21
- # wimax
- #
- # Look for IPASS style 'realm/', and if not found, look for
- # '@realm', and decide whether or not to proxy, based on
- # that.
- # IPASS
- #
- # If you are using multiple kinds of realms, you probably
- # want to set "ignore_null = yes" for all of them.
- # Otherwise, when the first style of realm doesn't match,
- # the other styles won't be checked.
- #
- suffix
- # ntdomain
- #
- # This module takes care of EAP-MD5, EAP-TLS, and EAP-LEAP
- # authentication.
- #
- # It also sets the EAP-Type attribute in the request
- # attribute list to the EAP type from the packet.
- #
- # As of 2.0, the EAP module returns "ok" in the authorize stage
- # for TTLS and PEAP. In 1.x, it never returned "ok" here, so
- # this change is compatible with older configurations.
- #
- # The example below uses module failover to avoid querying all
- # of the following modules if the EAP module returns "ok".
- # Therefore, your LDAP and/or SQL servers will not be queried
- # for the many packets that go back and forth to set up TTLS
- # or PEAP. The load on those servers will therefore be reduced.
- #
- eap {
- ok = return
- }
- #
- # Pull crypt'd passwords from /etc/passwd or /etc/shadow,
- # using the system API's to get the password. If you want
- # to read /etc/passwd or /etc/shadow directly, see the
- # passwd module in radiusd.conf.
- #
- # unix
- #
- # Read the 'users' file
- files
- #
- # Look in an SQL database. The schema of the database
- # is meant to mirror the "users" file.
- #
- # See "Authorization Queries" in sql.conf
- #sql
- #
- # If you are using /etc/smbpasswd, and are also doing
- # mschap authentication, the un-comment this line, and
- # configure the 'etc_smbpasswd' module, above.
- # etc_smbpasswd
- #
- # The ldap module will set Auth-Type to LDAP if it has not
- # already been set
- # ldap
- #
- # Enforce daily limits on time spent logged in.
- # daily
- #
- # Use the checkval module
- # checkval
- expiration
- logintime
- #
- # If no other module has claimed responsibility for
- # authentication, then try to use PAP. This allows the
- # other modules listed above to add a "known good" password
- # to the request, and to do nothing else. The PAP module
- # will then see that password, and use it to do PAP
- # authentication.
- #
- # This module should be listed last, so that the other modules
- # get a chance to set Auth-Type for themselves.
- #
- pap
- #
- # If "status_server = yes", then Status-Server messages are passed
- # through the following section, and ONLY the following section.
- # This permits you to do DB queries, for example. If the modules
- # listed here return "fail", then NO response is sent.
- #
- # Autz-Type Status-Server {
- #
- # }
- }
- # Authentication.
- #
- #
- # This section lists which modules are available for authentication.
- # Note that it does NOT mean 'try each module in order'. It means
- # that a module from the 'authorize' section adds a configuration
- # attribute 'Auth-Type := FOO'. That authentication type is then
- # used to pick the apropriate module from the list below.
- #
- # In general, you SHOULD NOT set the Auth-Type attribute. The server
- # will figure it out on its own, and will do the right thing. The
- # most common side effect of erroneously setting the Auth-Type
- # attribute is that one authentication method will work, but the
- # others will not.
- #
- # The common reasons to set the Auth-Type attribute by hand
- # is to either forcibly reject the user (Auth-Type := Reject),
- # or to or forcibly accept the user (Auth-Type := Accept).
- #
- # Note that Auth-Type := Accept will NOT work with EAP.
- #
- # Please do not put "unlang" configurations into the "authenticate"
- # section. Put them in the "post-auth" section instead. That's what
- # the post-auth section is for.
- #
- authenticate {
- #
- # PAP authentication, when a back-end database listed
- # in the 'authorize' section supplies a password. The
- # password can be clear-text, or encrypted.
- Auth-Type PAP {
- pap
- }
- #
- # Most people want CHAP authentication
- # A back-end database listed in the 'authorize' section
- # MUST supply a CLEAR TEXT password. Encrypted passwords
- # won't work.
- Auth-Type CHAP {
- chap
- }
- #
- # MSCHAP authentication.
- Auth-Type MS-CHAP {
- mschap
- }
- #
- # If you have a Cisco SIP server authenticating against
- # FreeRADIUS, uncomment the following line, and the 'digest'
- # line in the 'authorize' section.
- digest
- #
- # Pluggable Authentication Modules.
- # pam
- #
- # See 'man getpwent' for information on how the 'unix'
- # module checks the users password. Note that packets
- # containing CHAP-Password attributes CANNOT be authenticated
- # against /etc/passwd! See the FAQ for details.
- #
- # For normal "crypt" authentication, the "pap" module should
- # be used instead of the "unix" module. The "unix" module should
- # be used for authentication ONLY for compatibility with legacy
- # FreeRADIUS configurations.
- #
- unix
- # Uncomment it if you want to use ldap for authentication
- #
- # Note that this means "check plain-text password against
- # the ldap database", which means that EAP won't work,
- # as it does not supply a plain-text password.
- # Auth-Type LDAP {
- # ldap
- # }
- #
- # Allow EAP authentication.
- eap
- #
- # The older configurations sent a number of attributes in
- # Access-Challenge packets, which wasn't strictly correct.
- # If you want to filter out these attributes, uncomment
- # the following lines.
- #
- # Auth-Type eap {
- # eap {
- # handled = 1
- # }
- # if (handled && (Response-Packet-Type == Access-Challenge)) {
- # attr_filter.access_challenge.post-auth
- # handled # override the "updated" code from attr_filter
- # }
- # }
- }
- #
- # Pre-accounting. Decide which accounting type to use.
- #
- preacct {
- preprocess
- #
- # Session start times are *implied* in RADIUS.
- # The NAS never sends a "start time". Instead, it sends
- # a start packet, *possibly* with an Acct-Delay-Time.
- # The server is supposed to conclude that the start time
- # was "Acct-Delay-Time" seconds in the past.
- #
- # The code below creates an explicit start time, which can
- # then be used in other modules.
- #
- # The start time is: NOW - delay - session_length
- #
- # update request {
- # FreeRADIUS-Acct-Session-Start-Time = "%{expr: %l - %{%{Acct-Session-Time}:-0} - %{%{Acct-Delay-Time}:-0}}"
- # }
- #
- # Ensure that we have a semi-unique identifier for every
- # request, and many NAS boxes are broken.
- acct_unique
- #
- # Look for IPASS-style 'realm/', and if not found, look for
- # '@realm', and decide whether or not to proxy, based on
- # that.
- #
- # Accounting requests are generally proxied to the same
- # home server as authentication requests.
- # IPASS
- suffix
- # ntdomain
- #
- # Read the 'acct_users' file
- files
- }
- #
- # Accounting. Log the accounting data.
- #
- accounting {
- #
- # Create a 'detail'ed log of the packets.
- # Note that accounting requests which are proxied
- # are also logged in the detail file.
- detail
- # daily
- # Update the wtmp file
- #
- # If you don't use "radlast", you can delete this line.
- unix
- #
- # For Simultaneous-Use tracking.
- #
- # Due to packet losses in the network, the data here
- # may be incorrect. There is little we can do about it.
- radutmp
- # sradutmp
- # Return an address to the IP Pool when we see a stop record.
- # main_pool
- #
- # Log traffic to an SQL database.
- #
- # See "Accounting queries" in sql.conf
- #sql
- #
- # If you receive stop packets with zero session length,
- # they will NOT be logged in the database. The SQL module
- # will print a message (only in debugging mode), and will
- # return "noop".
- #
- # You can ignore these packets by uncommenting the following
- # three lines. Otherwise, the server will not respond to the
- # accounting request, and the NAS will retransmit.
- #
- # if (noop) {
- # ok
- # }
- #
- # Instead of sending the query to the SQL server,
- # write it into a log file.
- #
- # sql_log
- # Cisco VoIP specific bulk accounting
- # pgsql-voip
- # For Exec-Program and Exec-Program-Wait
- exec
- # Filter attributes from the accounting response.
- attr_filter.accounting_response
- #
- # See "Autz-Type Status-Server" for how this works.
- #
- # Acct-Type Status-Server {
- #
- # }
- }
- # Session database, used for checking Simultaneous-Use. Either the radutmp
- # or rlm_sql module can handle this.
- # The rlm_sql module is *much* faster
- session {
- radutmp
- #
- # See "Simultaneous Use Checking Queries" in sql.conf
- #sql
- }
- # Post-Authentication
- # Once we KNOW that the user has been authenticated, there are
- # additional steps we can take.
- post-auth {
- # Get an address from the IP Pool.
- # main_pool
- #
- # If you want to have a log of authentication replies,
- # un-comment the following line, and the 'detail reply_log'
- # section, above.
- # reply_log
- #
- # After authenticating the user, do another SQL query.
- #
- # See "Authentication Logging Queries" in sql.conf
- #sql
- #
- # Instead of sending the query to the server,
- # write it into a log file.
- #
- # sql_log
- #
- # Un-comment the following if you have set
- # 'edir_account_policy_check = yes' in the ldap module sub-section of
- # the 'modules' section.
- #
- # ldap
- # For Exec-Program and Exec-Program-Wait
- exec
- #
- # Calculate the various WiMAX keys. In order for this to work,
- # you will need to define the WiMAX NAI, usually via
- #
- # update request {
- # WiMAX-MN-NAI = "%{User-Name}"
- # }
- #
- # If you want various keys to be calculated, you will need to
- # update the reply with "template" values. The module will see
- # this, and replace the template values with the correct ones
- # taken from the cryptographic calculations. e.g.
- #
- # update reply {
- # WiMAX-FA-RK-Key = 0x00
- # WiMAX-MSK = "%{EAP-MSK}"
- # }
- #
- # You may want to delete the MS-MPPE-*-Keys from the reply,
- # as some WiMAX clients behave badly when those attributes
- # are included. See "raddb/modules/wimax", configuration
- # entry "delete_mppe_keys" for more information.
- #
- # wimax
- # 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
- # MAY be available during the authentication, or they may be
- # available only in the "post-auth" section.
- #
- # The first set of attributes contains information about the
- # issuing certificate which is being used. The second
- # contains information about the client certificate (if
- # available).
- #
- # update reply {
- # Reply-Message += "%{TLS-Cert-Serial}"
- # Reply-Message += "%{TLS-Cert-Expiration}"
- # Reply-Message += "%{TLS-Cert-Subject}"
- # Reply-Message += "%{TLS-Cert-Issuer}"
- # Reply-Message += "%{TLS-Cert-Common-Name}"
- #
- # Reply-Message += "%{TLS-Client-Cert-Serial}"
- # Reply-Message += "%{TLS-Client-Cert-Expiration}"
- # Reply-Message += "%{TLS-Client-Cert-Subject}"
- # Reply-Message += "%{TLS-Client-Cert-Issuer}"
- # Reply-Message += "%{TLS-Client-Cert-Common-Name}"
- # }
- # If the WiMAX module did it's work, you may want to do more
- # things here, like delete the MS-MPPE-*-Key attributes.
- #
- # if (updated) {
- # update reply {
- # MS-MPPE-Recv-Key !* 0x00
- # MS-MPPE-Send-Key !* 0x00
- # }
- # }
- #
- # Access-Reject packets are sent through the REJECT sub-section of the
- # post-auth section.
- #
- # Add the ldap module name (or instance) if you have set
- # 'edir_account_policy_check = yes' in the ldap module configuration
- #
- Post-Auth-Type REJECT {
- # log failed authentications in SQL, too.
- # sql
- attr_filter.access_reject
- }
- }
- #
- # When the server decides to proxy a request to a home server,
- # the proxied request is first passed through the pre-proxy
- # stage. This stage can re-write the request, or decide to
- # cancel the proxy.
- #
- # Only a few modules currently have this method.
- #
- pre-proxy {
- # attr_rewrite
- # Uncomment the following line if you want to change attributes
- # as defined in the preproxy_users file.
- # files
- # Uncomment the following line if you want to filter requests
- # sent to remote servers based on the rules defined in the
- # 'attrs.pre-proxy' file.
- # attr_filter.pre-proxy
- # If you want to have a log of packets proxied to a home
- # server, un-comment the following line, and the
- # 'detail pre_proxy_log' section, above.
- # pre_proxy_log
- }
- #
- # When the server receives a reply to a request it proxied
- # to a home server, the request may be massaged here, in the
- # post-proxy stage.
- #
- post-proxy {
- # If you want to have a log of replies from a home server,
- # un-comment the following line, and the 'detail post_proxy_log'
- # section, above.
- # post_proxy_log
- # attr_rewrite
- # Uncomment the following line if you want to filter replies from
- # remote proxies based on the rules defined in the 'attrs' file.
- # attr_filter.post-proxy
- #
- # If you are proxying LEAP, you MUST configure the EAP
- # module, and you MUST list it here, in the post-proxy
- # stage.
- #
- # You MUST also use the 'nostrip' option in the 'realm'
- # configuration. Otherwise, the User-Name attribute
- # in the proxied request will not match the user name
- # hidden inside of the EAP packet, and the end server will
- # reject the EAP request.
- #
- eap
- #
- # If the server tries to proxy a request and fails, then the
- # request is processed through the modules in this section.
- #
- # The main use of this section is to permit robust proxying
- # of accounting packets. The server can be configured to
- # proxy accounting packets as part of normal processing.
- # Then, if the home server goes down, accounting packets can
- # be logged to a local "detail" file, for processing with
- # radrelay. When the home server comes back up, radrelay
- # will read the detail file, and send the packets to the
- # home server.
- #
- # With this configuration, the server always responds to
- # Accounting-Requests from the NAS, but only writes
- # accounting packets to disk if the home server is down.
- #
- # Post-Proxy-Type Fail {
- # detail
- # }
- }
- ---------------------------------------------------------------------
- # -*- text -*-
- ##
- ## radiusd.conf -- FreeRADIUS server configuration file.
- ##
- ## http://www.freeradius.org/
- ## $Id$
- ##
- ######################################################################
- #
- # Read "man radiusd" before editing this file. See the section
- # titled DEBUGGING. It outlines a method where you can quickly
- # obtain the configuration you want, without running into
- # trouble.
- #
- # Run the server in debugging mode, and READ the output.
- #
- # $ radiusd -X
- #
- # We cannot emphasize this point strongly enough. The vast
- # majority of problems can be solved by carefully reading the
- # debugging output, which includes warnings about common issues,
- # and suggestions for how they may be fixed.
- #
- # There may be a lot of output, but look carefully for words like:
- # "warning", "error", "reject", or "failure". The messages there
- # will usually be enough to guide you to a solution.
- #
- # If you are going to ask a question on the mailing list, then
- # explain what you are trying to do, and include the output from
- # debugging mode (radiusd -X). Failure to do so means that all
- # of the responses to your question will be people telling you
- # to "post the output of radiusd -X".
- ######################################################################
- #
- # The location of other config files and logfiles are declared
- # in this file.
- #
- # Also general configuration for modules can be done in this
- # file, it is exported through the API to modules that ask for
- # it.
- #
- # See "man radiusd.conf" for documentation on the format of this
- # file. Note that the individual configuration items are NOT
- # documented in that "man" page. They are only documented here,
- # in the comments.
- #
- # As of 2.0.0, FreeRADIUS supports a simple processing language
- # in the "authorize", "authenticate", "accounting", etc. sections.
- # See "man unlang" for details.
- #
- prefix = /usr
- exec_prefix = /usr
- sysconfdir = /etc
- localstatedir = /var
- sbindir = ${exec_prefix}/sbin
- logdir = /var/log/freeradius
- raddbdir = /etc/freeradius
- radacctdir = ${logdir}/radacct
- #
- # name of the running server. See also the "-n" command-line option.
- name = freeradius
- # Location of config and logfiles.
- confdir = ${raddbdir}
- run_dir = ${localstatedir}/run/${name}
- # Should likely be ${localstatedir}/lib/radiusd
- db_dir = ${raddbdir}
- #
- # libdir: Where to find the rlm_* modules.
- #
- # This should be automatically set at configuration time.
- #
- # If the server builds and installs, but fails at execution time
- # with an 'undefined symbol' error, then you can use the libdir
- # directive to work around the problem.
- #
- # The cause is usually that a library has been installed on your
- # system in a place where the dynamic linker CANNOT find it. When
- # executing as root (or another user), your personal environment MAY
- # be set up to allow the dynamic linker to find the library. When
- # executing as a daemon, FreeRADIUS MAY NOT have the same
- # personalized configuration.
- #
- # To work around the problem, find out which library contains that symbol,
- # and add the directory containing that library to the end of 'libdir',
- # with a colon separating the directory names. NO spaces are allowed.
- #
- # e.g. libdir = /usr/local/lib:/opt/package/lib
- #
- # You can also try setting the LD_LIBRARY_PATH environment variable
- # in a script which starts the server.
- #
- # If that does not work, then you can re-configure and re-build the
- # server to NOT use shared libraries, via:
- #
- # ./configure --disable-shared
- # make
- # make install
- #
- libdir = /usr/lib/freeradius
- # pidfile: Where to place the PID of the RADIUS server.
- #
- # The server may be signalled while it's running by using this
- # file.
- #
- # This file is written when ONLY running in daemon mode.
- #
- # e.g.: kill -HUP `cat /var/run/radiusd/radiusd.pid`
- #
- pidfile = ${run_dir}/${name}.pid
- # chroot: directory where the server does "chroot".
- #
- # The chroot is done very early in the process of starting the server.
- # After the chroot has been performed it switches to the "user" listed
- # below (which MUST be specified). If "group" is specified, it switchs
- # to that group, too. Any other groups listed for the specified "user"
- # in "/etc/group" are also added as part of this process.
- #
- # The current working directory (chdir / cd) is left *outside* of the
- # chroot until all of the modules have been initialized. This allows
- # the "raddb" directory to be left outside of the chroot. Once the
- # modules have been initialized, it does a "chdir" to ${logdir}. This
- # means that it should be impossible to break out of the chroot.
- #
- # If you are worried about security issues related to this use of chdir,
- # then simply ensure that the "raddb" directory is inside of the chroot,
- # end be sure to do "cd raddb" BEFORE starting the server.
- #
- # If the server is statically linked, then the only files that have
- # to exist in the chroot are ${run_dir} and ${logdir}. If you do the
- # "cd raddb" as discussed above, then the "raddb" directory has to be
- # inside of the chroot directory, too.
- #
- #chroot = /path/to/chroot/directory
- # user/group: The name (or #number) of the user/group to run radiusd as.
- #
- # If these are commented out, the server will run as the user/group
- # that started it. In order to change to a different user/group, you
- # MUST be root ( or have root privleges ) to start the server.
- #
- # We STRONGLY recommend that you run the server with as few permissions
- # as possible. That is, if you're not using shadow passwords, the
- # user and group items below should be set to radius'.
- #
- # NOTE that some kernels refuse to setgid(group) when the value of
- # (unsigned)group is above 60000; don't use group nobody on these systems!
- #
- # On systems with shadow passwords, you might have to set 'group = shadow'
- # for the server to be able to read the shadow password file. If you can
- # authenticate users while in debug mode, but not in daemon mode, it may be
- # that the debugging mode server is running as a user that can read the
- # shadow info, and the user listed below can not.
- #
- # The server will also try to use "initgroups" to read /etc/groups.
- # It will join all groups where "user" is a member. This can allow
- # for some finer-grained access controls.
- #
- user = freerad
- group = freerad
- # max_request_time: 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.
- #
- # WARNING: If you notice that requests take a long time to be handled,
- # then this MAY INDICATE a bug in the server, in one of the modules
- # used to handle a request, OR in your local configuration.
- #
- # This problem is most often seen when using an SQL database. If it takes
- # more than a second or two to receive an answer from the SQL database,
- # then it probably means that you haven't indexed the database. See your
- # SQL server documentation for more information.
- #
- # Useful range of values: 5 to 120
- #
- max_request_time = 30
- # cleanup_delay: 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 seperate 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'.)
- #
- # Useful range of values: 2 to 10
- #
- cleanup_delay = 5
- # max_requests: The maximum number of requests which the server keeps
- # track of. This should be 256 multiplied by the number of clients.
- # e.g. 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.
- #
- # Useful range of values: 256 to infinity
- #
- max_requests = 1024
- # listen: Make the server listen on a particular IP address, and send
- # replies out from that address. This directive is most useful for
- # hosts with multiple IP addresses on one interface.
- #
- # If you want the server to listen on additional addresses, or on
- # additionnal ports, you can use multiple "listen" sections.
- #
- # Each section make the server listen for only one type of packet,
- # therefore authentication and accounting have to be configured in
- # different sections.
- #
- # The server ignore all "listen" section if you are using '-i' and '-p'
- # on the command line.
- #
- listen {
- # Type of packets to listen for.
- # Allowed values are:
- # auth listen for authentication packets
- # acct listen for accounting packets
- # proxy IP to use for sending proxied packets
- # detail Read from the detail file. For examples, see
- # raddb/sites-available/copy-acct-to-home-server
- # status listen for Status-Server packets. For examples,
- # see raddb/sites-available/status
- # coa listen for CoA-Request and Disconnect-Request
- # packets. For examples, see the file
- # raddb/sites-available/coa-server
- #
- type = auth
- # Note: "type = proxy" lets you control the source IP used for
- # proxying packets, with some limitations:
- #
- # * A proxy listener CANNOT be used in a virtual server section.
- # * You should probably set "port = 0".
- # * Any "clients" configuration will be ignored.
- #
- # See also proxy.conf, and the "src_ipaddr" configuration entry
- # in the sample "home_server" section. When you specify the
- # source IP address for packets sent to a home server, the
- # proxy listeners are automatically created.
- # IP address on which to listen.
- # Allowed values are:
- # dotted quad (1.2.3.4)
- # hostname (radius.example.com)
- # wildcard (*)
- ipaddr = *
- # OR, you can use an IPv6 address, but not both
- # at the same time.
- # ipv6addr = :: # any. ::1 == localhost
- # Port on which to listen.
- # Allowed values are:
- # integer port number (1812)
- # 0 means "use /etc/services for the proper port"
- port = 0
- # Some systems support binding to an interface, in addition
- # to the IP address. This feature isn't strictly necessary,
- # but for sites with many IP addresses on one interface,
- # it's useful to say "listen on all addresses for eth0".
- #
- # If your system does not support this feature, you will
- # get an error if you try to use it.
- #
- # interface = eth0
- # Per-socket lists of clients. This is a very useful feature.
- #
- # The name here is a reference to a section elsewhere in
- # radiusd.conf, or clients.conf. Having the name as
- # a reference allows multiple sockets to use the same
- # set of clients.
- #
- # If this configuration is used, then the global list of clients
- # is IGNORED for this "listen" section. Take care configuring
- # this feature, to ensure you don't accidentally disable a
- # client you need.
- #
- # See clients.conf for the configuration of "per_socket_clients".
- #
- # clients = per_socket_clients
- }
- # This second "listen" section is for listening on the accounting
- # port, too.
- #
- listen {
- ipaddr = *
- # ipv6addr = ::
- port = 0
- type = acct
- # interface = eth0
- # clients = per_socket_clients
- }
- # hostname_lookups: Log the names of clients or just their IP addresses
- # e.g., www.freeradius.org (on) or 206.47.27.232 (off).
- #
- # The default is 'off' because it would be overall better for the net
- # if people had to knowingly turn this feature on, since enabling it
- # means that each client request will result in AT LEAST one lookup
- # request to the nameserver. Enabling hostname_lookups will also
- # mean that your server may stop randomly for 30 seconds from time
- # to time, if the DNS requests take too long.
- #
- # Turning hostname lookups off also means that the server won't block
- # for 30 seconds, if it sees an IP address which has no name associated
- # with it.
- #
- # allowed values: {no, yes}
- #
- hostname_lookups = no
- # Core dumps are a bad thing. This should only be set to 'yes'
- # if you're debugging a problem with the server.
- #
- # allowed values: {no, yes}
- #
- allow_core_dumps = no
- # Regular expressions
- #
- # These items are set at configure time. If they're set to "yes",
- # then setting them to "no" turns off regular expression support.
- #
- # If they're set to "no" at configure time, then setting them to "yes"
- # WILL NOT WORK. It will give you an error.
- #
- regular_expressions = yes
- extended_expressions = yes
- #
- # Logging section. The various "log_*" configuration items
- # will eventually be moved here.
- #
- log {
- #
- # Destination for log messages. This can be one of:
- #
- # files - log to "file", as defined below.
- # syslog - to syslog (see also the "syslog_facility", below.
- # stdout - standard output
- # stderr - standard error.
- #
- # The command-line option "-X" over-rides this option, and forces
- # logging to go to stdout.
- #
- destination = files
- #
- # The logging messages for the server are appended to the
- # tail of this file if destination == "files"
- #
- # If the server is running in debugging mode, this file is
- # NOT used.
- #
- file = ${logdir}/radius.log
- #
- # If this configuration parameter is set, then log messages for
- # a *request* go to this file, rather than to radius.log.
- #
- # i.e. This is a log file per request, once the server has accepted
- # the request as being from a valid client. Messages that are
- # not associated with a request still go to radius.log.
- #
- # Not all log messages in the server core have been updated to use
- # this new internal API. As a result, some messages will still
- # go to radius.log. Please submit patches to fix this behavior.
- #
- # The file name is expanded dynamically. You should ONLY user
- # server-side attributes for the filename (e.g. things you control).
- # Using this feature MAY also slow down the server substantially,
- # especially if you do thinks like SQL calls as part of the
- # expansion of the filename.
- #
- # The name of the log file should use attributes that don't change
- # over the lifetime of a request, such as User-Name,
- # Virtual-Server or Packet-Src-IP-Address. Otherwise, the log
- # messages will be distributed over multiple files.
- #
- # Logging can be enabled for an individual request by a special
- # dynamic expansion macro: %{debug: 1}, where the debug level
- # for this request is set to '1' (or 2, 3, etc.). e.g.
- #
- # ...
- # update control {
- # Tmp-String-0 = "%{debug:1}"
- # }
- # ...
- #
- # The attribute that the value is assigned to is unimportant,
- # and should be a "throw-away" attribute with no side effects.
- #
- #requests = ${logdir}/radiusd-%{%{Virtual-Server}:-DEFAULT}-%Y%m%d.log
- #
- # Which syslog facility to use, if ${destination} == "syslog"
- #
- # The exact values permitted here are OS-dependent. You probably
- # don't want to change this.
- #
- syslog_facility = daemon
- # Log the full User-Name attribute, as it was found in the request.
- #
- # allowed values: {no, yes}
- #
- stripped_names = no
- # Log authentication requests to the log file.
- #
- # allowed values: {no, yes}
- #
- auth = no
- # Log passwords with the authentication requests.
- # auth_badpass - logs password if it's rejected
- # auth_goodpass - logs password if it's correct
- #
- # allowed values: {no, yes}
- #
- auth_badpass = no
- auth_goodpass = no
- # Log additional text at the end of the "Login OK" messages.
- # for these to work, the "auth" and "auth_goopass" or "auth_badpass"
- # configurations above have to be set to "yes".
- #
- # The strings below are dynamically expanded, which means that
- # you can put anything you want in them. However, note that
- # this expansion can be slow, and can negatively impact server
- # performance.
- #
- # msg_goodpass = ""
- # msg_badpass = ""
- }
- # The program to execute to do concurrency checks.
- checkrad = ${sbindir}/checkrad
- # SECURITY CONFIGURATION
- #
- # There may be multiple methods of attacking on the server. This
- # section holds the configuration items which minimize the impact
- # of those attacks
- #
- security {
- #
- # max_attributes: The maximum number of attributes
- # permitted in a RADIUS packet. Packets which have MORE
- # than this number of attributes in them will be dropped.
- #
- # If this number is set too low, then no RADIUS packets
- # will be accepted.
- #
- # If this number is set too high, then an attacker may be
- # able to send a small number of packets which will cause
- # the server to use all available memory on the machine.
- #
- # Setting this number to 0 means "allow any number of attributes"
- max_attributes = 200
- #
- # reject_delay: When sending an Access-Reject, it can be
- # delayed for a few seconds. This may help slow down a DoS
- # attack. It also helps to slow down people trying to brute-force
- # crack a users password.
- #
- # Setting this number to 0 means "send rejects immediately"
- #
- # If this number is set higher than 'cleanup_delay', then the
- # rejects will be sent at 'cleanup_delay' time, when the request
- # is deleted from the internal cache of requests.
- #
- # Useful ranges: 1 to 5
- reject_delay = 1
- #
- # status_server: Whether or not the server will respond
- # to Status-Server requests.
- #
- # When sent a Status-Server message, the server responds with
- # an Access-Accept or Accounting-Response packet.
- #
- # This is mainly useful for administrators who want to "ping"
- # the server, without adding test users, or creating fake
- # accounting packets.
- #
- # It's also useful when a NAS marks a RADIUS server "dead".
- # The NAS can periodically "ping" the server with a Status-Server
- # packet. If the server responds, it must be alive, and the
- # NAS can start using it for real requests.
- #
- # See also raddb/sites-available/status
- #
- status_server = yes
- }
- # PROXY CONFIGURATION
- #
- # proxy_requests: Turns proxying of RADIUS requests on or off.
- #
- # The server has proxying turned on by default. If your system is NOT
- # set up to proxy requests to another server, then you can turn proxying
- # off here. This will save a small amount of resources on the server.
- #
- # If you have proxying turned off, and your configuration files say
- # to proxy a request, then an error message will be logged.
- #
- # To disable proxying, change the "yes" to "no", and comment the
- # $INCLUDE line.
- #
- # allowed values: {no, yes}
- #
- proxy_requests = yes
- $INCLUDE proxy.conf
- # CLIENTS CONFIGURATION
- #
- # Client configuration is defined in "clients.conf".
- #
- # The 'clients.conf' file contains all of the information from the old
- # 'clients' and 'naslist' configuration files. We recommend that you
- # do NOT use 'client's or 'naslist', although they are still
- # supported.
- #
- # Anything listed in 'clients.conf' will take precedence over the
- # information from the old-style configuration files.
- #
- $INCLUDE clients.conf
- # THREAD POOL CONFIGURATION
- #
- # The thread pool is a long-lived group of threads which
- # take turns (round-robin) handling any incoming requests.
- #
- # You probably want to have a few spare threads around,
- # so that high-load situations can be handled immediately. If you
- # don't have any spare threads, then the request handling will
- # be delayed while a new thread is created, and added to the pool.
- #
- # You probably don't want too many spare threads around,
- # otherwise they'll be sitting there taking up resources, and
- # not doing anything productive.
- #
- # The numbers given below should be adequate for most situations.
- #
- thread pool {
- # Number of servers to start initially --- should be a reasonable
- # ballpark figure.
- start_servers = 5
- # Limit on the total number of servers running.
- #
- # If this limit is ever reached, clients will be LOCKED OUT, so it
- # should NOT BE SET TOO LOW. It is intended mainly as a brake to
- # keep a runaway server from taking the system with it as it spirals
- # down...
- #
- # You may find that the server is regularly reaching the
- # 'max_servers' number of threads, and that increasing
- # 'max_servers' doesn't seem to make much difference.
- #
- # If this is the case, then the problem is MOST LIKELY that
- # your back-end databases are taking too long to respond, and
- # are preventing the server from responding in a timely manner.
- #
- # The solution is NOT do keep increasing the 'max_servers'
- # value, but instead to fix the underlying cause of the
- # problem: slow database, or 'hostname_lookups=yes'.
- #
- # For more information, see 'max_request_time', above.
- #
- max_servers = 32
- # Server-pool size regulation. Rather than making you guess
- # how many servers you need, FreeRADIUS dynamically adapts to
- # the load it sees, that is, it tries to maintain enough
- # servers to handle the current load, plus a few spare
- # servers to handle transient load spikes.
- #
- # It does this by periodically checking how many servers are
- # waiting for a request. If there are fewer than
- # min_spare_servers, it creates a new spare. If there are
- # more than max_spare_servers, some of the spares die off.
- # The default values are probably OK for most sites.
- #
- min_spare_servers = 3
- max_spare_servers = 10
- # When the server receives a packet, it places it onto an
- # internal queue, where the worker threads (configured above)
- # pick it up for processing. The maximum size of that queue
- # is given here.
- #
- # When the queue is full, any new packets will be silently
- # discarded.
- #
- # The most common cause of the queue being full is that the
- # server is dependent on a slow database, and it has received
- # a large "spike" of traffic. When that happens, there is
- # very little you can do other than make sure the server
- # receives less traffic, or make sure that the database can
- # handle the load.
- #
- # max_queue_size = 65536
- # There may be memory leaks or resource allocation problems with
- # the server. If so, set this value to 300 or so, so that the
- # resources will be cleaned up periodically.
- #
- # This should only be necessary if there are serious bugs in the
- # server which have not yet been fixed.
- #
- # '0' is a special value meaning 'infinity', or 'the servers never
- # exit'
- max_requests_per_server = 0
- }
- # MODULE CONFIGURATION
- #
- # The names and configuration of each module is located in this section.
- #
- # After the modules are defined here, they may be referred to by name,
- # in other sections of this configuration file.
- #
- modules {
- #
- # Each module has a configuration as follows:
- #
- # name [ instance ] {
- # config_item = value
- # ...
- # }
- #
- # The 'name' is used to load the 'rlm_name' library
- # which implements the functionality of the module.
- #
- # The 'instance' is optional. To have two different instances
- # of a module, it first must be referred to by 'name'.
- # The different copies of the module are then created by
- # inventing two 'instance' names, e.g. 'instance1' and 'instance2'
- #
- # The instance names can then be used in later configuration
- # INSTEAD of the original 'name'. See the 'radutmp' configuration
- # for an example.
- #
- #
- # As of 2.0.5, most of the module configurations are in a
- # sub-directory. Files matching the regex /[a-zA-Z0-9_.]+/
- # are loaded. The modules are initialized ONLY if they are
- # referenced in a processing section, such as authorize,
- # authenticate, accounting, pre/post-proxy, etc.
- #
- $INCLUDE ${confdir}/modules/
- # Extensible Authentication Protocol
- #
- # For all EAP related authentications.
- # Now in another file, because it is very large.
- #
- $INCLUDE eap.conf
- # Include another file that has the SQL-related configuration.
- # This is another file only because it tends to be big.
- #
- #$INCLUDE sql.conf
- #
- # This module is an SQL enabled version of the counter module.
- #
- # Rather than maintaining seperate (GDBM) databases of
- # accounting info for each counter, this module uses the data
- # stored in the raddacct table by the sql modules. This
- # module NEVER does any database INSERTs or UPDATEs. It is
- # totally dependent on the SQL module to process Accounting
- # packets.
- #
- # $INCLUDE sql/mysql/counter.conf
- #
- # IP addresses managed in an SQL table.
- #
- # $INCLUDE sqlippool.conf
- }
- # Instantiation
- #
- # This section orders the loading of the modules. Modules
- # listed here will get loaded BEFORE the later sections like
- # authorize, authenticate, etc. get examined.
- #
- # This section is not strictly needed. When a section like
- # authorize refers to a module, it's automatically loaded and
- # initialized. However, some modules may not be listed in any
- # of the following sections, so they can be listed here.
- #
- # Also, listing modules here ensures that you have control over
- # the order in which they are initalized. If one module needs
- # something defined by another module, you can list them in order
- # here, and ensure that the configuration will be OK.
- #
- instantiate {
- #
- # Allows the execution of external scripts.
- # The entire command line (and output) must fit into 253 bytes.
- #
- # e.g. Framed-Pool = `%{exec:/bin/echo foo}`
- exec
- #
- # The expression module doesn't do authorization,
- # authentication, or accounting. It only does dynamic
- # translation, of the form:
- #
- # Session-Timeout = `%{expr:2 + 3}`
- #
- # So the module needs to be instantiated, but CANNOT be
- # listed in any other section. See 'doc/rlm_expr' for
- # more information.
- #
- expr
- #
- # We add the counter module here so that it registers
- # the check-name attribute before any module which sets
- # it
- # daily
- expiration
- logintime
- # subsections here can be thought of as "virtual" modules.
- #
- # e.g. If you have two redundant SQL servers, and you want to
- # use them in the authorize and accounting sections, you could
- # place a "redundant" block in each section, containing the
- # exact same text. Or, you could uncomment the following
- # lines, and list "redundant_sql" in the authorize and
- # accounting sections.
- #
- #redundant redundant_sql {
- # sql1
- # sql2
- #}
- }
- ######################################################################
- #
- # Policies that can be applied in multiple places are listed
- # globally. That way, they can be defined once, and referred
- # to multiple times.
- #
- ######################################################################
- $INCLUDE policy.conf
- ######################################################################
- #
- # Load virtual servers.
- #
- # This next $INCLUDE line loads files in the directory that
- # match the regular expression: /[a-zA-Z0-9_.]+/
- #
- # It allows you to define new virtual servers simply by placing
- # a file into the raddb/sites-enabled/ directory.
- #
- $INCLUDE sites-enabled/
- ######################################################################
- #
- # All of the other configuration sections like "authorize {}",
- # "authenticate {}", "accounting {}", have been moved to the
- # the file:
- #
- # raddb/sites-available/default
- #
- # This is the "default" virtual server that has the same
- # configuration as in version 1.0.x and 1.1.x. The default
- # installation enables this virtual server. You should
- # edit it to create policies for your local site.
- #
- # For more documentation on virtual servers, see:
- #
- # raddb/sites-available/README
- #
- ######################################################################
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement