Dear Radius,
Please read doc/bugs on how to enable coredumps and debug info and send
gdb bt results back to list.
--Tuesday, August 5, 2003, 6:59:02 PM, you wrote to [EMAIL PROTECTED]:
R> Hi you all,
R> Just started using FreeRadius 0.9.0 on FreeBSD 4.8-Stable. I want to use
R> FreeBSD to authenticate VPN users connecting to my Vigor 2300 and Vigor 2200
R> routers. They support several different VPN's and authentication. I've got
R> things working now with PAP, I think I won't get CHAP working by only using
R> a passwd file on FreeBSD. However getting it to work with MSCHAP (v1/v2)
R> shouldn't be a problem. I red the doc/rlm_mschap and folled the instructions
R> given.
R> But when connecting while using MSCHAP I get a core dump on radiusd and all
R> stops working.
R> when I use radtest on terminal 1:
R> [EMAIL PROTECTED] radtest radius radius localhost 0 testing123
R> Sending Access-Request of id 38 to 127.0.0.1:1812
R> User-Name = "radius"
R> User-Password = "radius"
R> NAS-IP-Address = piersma.com
R> NAS-Port = 0
R> rad_recv: Access-Accept packet from host 127.0.0.1:1812, id=38, length=20
R> [EMAIL PROTECTED] radtest radius radius localhost 0 testing123
R> Sending Access-Request of id 51 to 127.0.0.1:1812
R> User-Name = "radius"
R> User-Password = "radius"
R> NAS-IP-Address = piersma.com
R> NAS-Port = 0
R> Re-sending Access-Request of id 51 to 127.0.0.1:1812
R> User-Name = "radius"
R> User-Password = "\tn\264\234\370\223k\237hX\221ax\3606\211"
R> NAS-IP-Address = piersma.com
R> NAS-Port = 0
R> Re-sending Access-Request of id 51 to 127.0.0.1:1812
R> User-Name = "radius"
R> User-Password = "\tn\264\234\370\223k\237hX\221ax\3606\211"
R> NAS-IP-Address = piersma.com
R> NAS-Port = 0
R> (CTRL-C, just fails after 8 times)
R> I get this on terminal 2:
R> [EMAIL PROTECTED] radiusd -xx -s
R> Starting - reading configuration files ...
R> reread_config: reading radiusd.conf
R> Config: including file: /usr/local/etc/raddb/proxy.conf
R> Config: including file: /usr/local/etc/raddb/clients.conf
R> Config: including file: /usr/local/etc/raddb/snmp.conf
R> Config: including file: /usr/local/etc/raddb/sql.conf
R> main: prefix = "/usr/local"
R> main: localstatedir = "/usr/local/var"
R> main: logdir = "/usr/local/var/log/radius"
R> main: libdir = "/usr/local/lib"
R> main: radacctdir = "/usr/local/var/log/radius/radacct"
R> main: hostname_lookups = no
R> main: max_request_time = 30
R> main: cleanup_delay = 5
R> main: max_requests = 1024
R> main: delete_blocked_requests = 0
R> main: port = 0
R> main: allow_core_dumps = no
R> main: log_stripped_names = no
R> main: log_file = "/usr/local/var/log/radius/radius.log"
R> main: log_auth = yes
R> main: log_auth_badpass = yes
R> main: log_auth_goodpass = yes
R> main: pidfile = "/usr/local/var/run/radiusd/radiusd.pid"
R> main: user = "(null)"
R> main: group = "(null)"
R> main: usercollide = no
R> main: lower_user = "no"
R> main: lower_pass = "no"
R> main: nospace_user = "no"
R> main: nospace_pass = "no"
R> main: checkrad = "/usr/local/sbin/checkrad"
R> main: proxy_requests = yes
R> proxy: retry_delay = 5
R> proxy: retry_count = 3
R> proxy: synchronous = no
R> proxy: default_fallback = yes
R> proxy: dead_time = 120
R> proxy: post_proxy_authorize = yes
R> proxy: wake_all_if_all_dead = no
R> security: max_attributes = 200
R> security: reject_delay = 1
R> security: status_server = no
R> main: debug_level = 0
R> read_config_files: reading dictionary
R> read_config_files: reading naslist
R> Using deprecated naslist file. Support for this will go away soon.
R> read_config_files: reading clients
R> Using deprecated clients file. Support for this will go away soon.
R> read_config_files: reading realms
R> Using deprecated realms file. Support for this will go away soon.
R> radiusd: entering modules setup
R> Module: Library search path is /usr/local/lib
R> Module: Loaded expr
R> Module: Instantiated expr (expr)
R> Module: Loaded PAP
R> pap: encryption_scheme = "crypt"
R> Module: Instantiated pap (pap)
R> Module: Loaded CHAP
R> Module: Instantiated chap (chap)
R> Module: Loaded MS-CHAP
R> mschap: use_mppe = no
R> mschap: require_encryption = no
R> mschap: require_strong = no
R> mschap: passwd = "(null)"
R> mschap: authtype = "MS-CHAP"
R> Module: Instantiated mschap (mschap)
R> Module: Loaded System
R> unix: cache = no
R> unix: passwd = "(null)"
R> unix: shadow = "(null)"
R> unix: group = "/etc/group"
R> unix: radwtmp = "/usr/local/var/log/radius/radwtmp"
R> unix: usegroup = no
R> unix: cache_reload = 600
R> Module: Instantiated unix (unix)
R> Module: Loaded eap
R> eap: default_eap_type = "md5"
R> eap: timer_expire = 60
R> rlm_eap: Loaded and initialized the type md5
R> rlm_eap: Loaded and initialized the type leap
R> Module: Instantiated eap (eap)
R> Module: Loaded preprocess
R> preprocess: huntgroups = "/usr/local/etc/raddb/huntgroups"
R> preprocess: hints = "/usr/local/etc/raddb/hints"
R> preprocess: with_ascend_hack = no
R> preprocess: ascend_channels_per_line = 23
R> preprocess: with_ntdomain_hack = no
R> preprocess: with_specialix_jetstream_hack = no
R> preprocess: with_cisco_vsa_hack = no
R> Module: Instantiated preprocess (preprocess)
R> Module: Loaded realm
R> realm: format = "suffix"
R> realm: delimiter = "@"
R> Module: Instantiated realm (suffix)
R> Module: Loaded files
R> files: usersfile = "/usr/local/etc/raddb/users"
R> files: acctusersfile = "/usr/local/etc/raddb/acct_users"
R> files: preproxy_usersfile = "/usr/local/etc/raddb/preproxy_users"
R> files: compat = "no"
R> Module: Instantiated files (files)
R> Module: Loaded passwd
R> passwd: filename = "/usr/local/private/smbpasswd"
R> passwd: format =
R> "*User-Name::LM-Password:NT-Password:SMB-Account-CTRL-TEXT::"
R> passwd: authtype = "MS-CHAP"
R> passwd: delimiter = ":"
R> passwd: ignorenislike = no
R> passwd: allowmultiplekeys = no
R> passwd: hashsize = 100
R> rlm_passwd: nfields: 7 keyfield 0(User-Name) listable: no
R> Module: Instantiated passwd (etc_smbpasswd)
R> Module: Loaded Acct-Unique-Session-Id
R> acct_unique: key = "User-Name, Acct-Session-Id, NAS-IP-Address,
R> Client-IP-Address, NAS-Port-Id"
R> Module: Instantiated acct_unique (acct_unique)
R> Module: Loaded detail
R> detail: detailfile =
R> "/usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d"
R> detail: detailperm = 384
R> detail: dirperm = 493
R> detail: locking = no
R> Module: Instantiated detail (detail)
R> Module: Loaded radutmp
R> radutmp: filename = "/usr/local/var/log/radius/radutmp"
R> radutmp: username = "%{User-Name}"
R> radutmp: case_sensitive = yes
R> radutmp: check_with_nas = yes
R> radutmp: perm = 384
R> radutmp: callerid = yes
R> Module: Instantiated radutmp (radutmp)
R> Listening on IP address *, ports 1812/udp and 1813/udp, with proxy on
R> 1814/udp.
R> Ready to process requests.
R> rad_recv: Access-Request packet from host 127.0.0.1:1660, id=203, length=58
R> User-Name = "radius"
R> User-Password = "radius"
R> NAS-IP-Address = 255.255.255.255
R> NAS-Port = 0
R> modcall: entering group authorize
R> modcall[authorize]: module "preprocess" returns ok
R> modcall[authorize]: module "chap" returns noop
R> rlm_eap: EAP-Message not found
R> modcall[authorize]: module "eap" returns noop
R> rlm_realm: No '@' in User-Name = "radius", looking up realm NULL
R> rlm_realm: No such realm "NULL"
R> modcall[authorize]: module "suffix" returns noop
R> users: Matched DEFAULT at 152
R> modcall[authorize]: module "files" returns ok
R> rlm_passwd: Added LM-Password: '22E287599B15A61EAAD3B435B51404EE' to
R> config_items
R> rlm_passwd: Added NT-Password: '006CCC216FF80767832CD0BF82881615' to
R> config_items
R> rlm_passwd: Added SMB-Account-CTRL-TEXT: '[UX ]' to config_items
R> rlm_passwd: Adding Auth-Type: MS-CHAP
R> modcall[authorize]: module "etc_smbpasswd" returns ok
R> modcall[authorize]: module "mschap" returns noop
R> modcall: group authorize returns ok
R> rad_check_password: Found Auth-Type System
R> rad_check_password: Found Auth-Type MS-CHAP
R> Warning: Found 2 auth-types on request for user 'radius'
R> auth: type "MS-CHAP"
R> modcall: entering group Auth-Type
R> Segmentation fault (core dumped)
R> So that isn't working. Maybe I made some configuration error somewhere. I
R> played with the mppe settings and encryption settings in radiusd.conf but
R> that doesn't seem to make a diff.
R> My radiusd.conf:
R> ##
R> ## radiusd.conf -- FreeRADIUS server configuration file.
R> ##
R> ## http://www.freeradius.org/
R> ## $Id: radiusd.conf.in,v 1.148 2003/06/24 12:54:05 3APA3A Exp $
R> ##
R> # The location of other config files and
R> # logfiles are declared in this file
R> #
R> # Also general configuration for modules can be done
R> # in this file, it is exported through the API to
R> # modules that ask for it.
R> #
R> # The configuration variables defined here are of the form ${foo}
R> # They are local to this file, and do not change from request to
R> # request.
R> #
R> # The per-request variables are of the form %{Attribute-Name}, and
R> # are taken from the values of the attribute in the incoming
R> # request. See 'doc/variables.txt' for more information.
R> prefix = /usr/local
R> exec_prefix = ${prefix}
R> sysconfdir = ${prefix}/etc
R> localstatedir = ${prefix}/var
R> sbindir = ${exec_prefix}/sbin
R> logdir = ${localstatedir}/log/radius
R> raddbdir = ${sysconfdir}/raddb
R> radacctdir = ${logdir}/radacct
R> # Location of config and logfiles.
R> confdir = ${raddbdir}
R> run_dir = ${localstatedir}/run/radiusd
R> #
R> # The logging messages for the server are appended to the
R> # tail of this file.
R> #
R> log_file = ${logdir}/radius.log
R> #
R> # libdir: Where to find the rlm_* modules.
R> #
R> # This should be automatically set at configuration time.
R> #
R> # If the server builds and installs, but fails at execution time
R> # with an 'undefined symbol' error, then you can use the libdir
R> # directive to work around the problem.
R> #
R> # The cause is usually that a library has been installed on your
R> # system in a place where the dynamic linker CANNOT find it. When
R> # executing as root (or another user), your personal environment MAY
R> # be set up to allow the dynamic linker to find the library. When
R> # executing as a daemon, FreeRADIUS MAY NOT have the same
R> # personalized configuration.
R> #
R> # To work around the problem, find out which library contains that symbol,
R> # and add the directory containing that library to the end of 'libdir',
R> # with a colon separating the directory names. NO spaces are allowed.
R> #
R> # e.g. libdir = /usr/local/lib:/opt/package/lib
R> #
R> # You can also try setting the LD_LIBRARY_PATH environment variable
R> # in a script which starts the server.
R> #
R> # If that does not work, then you can re-configure and re-build the
R> # server to NOT use shared libraries, via:
R> #
R> # ./configure --disable-shared
R> # make
R> # make install
R> #
R> libdir = ${exec_prefix}/lib
R> # pidfile: Where to place the PID of the RADIUS server.
R> #
R> # The server may be signalled while it's running by using this
R> # file.
R> #
R> # This file is written when ONLY running in daemon mode.
R> #
R> # e.g.: kill -HUP `cat /var/run/radiusd/radiusd.pid`
R> #
R> pidfile = ${run_dir}/radiusd.pid
R> # user/group: The name (or #number) of the user/group to run radiusd as.
R> #
R> # If these are commented out, the server will run as the user/group
R> # that started it. In order to change to a different user/group, you
R> # MUST be root ( or have root privleges ) to start the server.
R> #
R> # We STRONGLY recommend that you run the server with as few permissions
R> # as possible. That is, if you're not using shadow passwords, the
R> # user and group items below should be set to 'nobody'.
R> #
R> # On SCO (ODT 3) use "user = nouser" and "group = nogroup".
R> #
R> # NOTE that some kernels refuse to setgid(group) when the value of
R> # (unsigned)group is above 60000; don't use group nobody on these systems!
R> #
R> # On systems with shadow passwords, you might have to set 'group = shadow'
R> # for the server to be able to read the shadow password file. If you can
R> # authenticate users while in debug mode, but not in daemon mode, it may be
R> # that the debugging mode server is running as a user that can read the
R> # shadow info, and the user listed below can not.
R> #
R> #user = nobody
R> #group = nobody
R> # max_request_time: The maximum time (in seconds) to handle a request.
R> #
R> # Requests which take more time than this to process may be killed, and
R> # a REJECT message is returned.
R> #
R> # WARNING: If you notice that requests take a long time to be handled,
R> # then this MAY INDICATE a bug in the server, in one of the modules
R> # used to handle a request, OR in your local configuration.
R> #
R> # This problem is most often seen when using an SQL database. If it takes
R> # more than a second or two to receive an answer from the SQL database,
R> # then it probably means that you haven't indexed the database. See your
R> # SQL server documentation for more information.
R> #
R> # Useful range of values: 5 to 120
R> #
R> max_request_time = 30
R> # delete_blocked_requests: If the request takes MORE THAN 'max_request_time'
R> # to be handled, then maybe the server should delete it.
R> #
R> # If you're running in threaded, or thread pool mode, this setting
R> # should probably be 'no'. Setting it to 'yes' when using a threaded
R> # server MAY cause the server to crash!
R> #
R> delete_blocked_requests = no
R> # cleanup_delay: The time to wait (in seconds) before cleaning up
R> # a reply which was sent to the NAS.
R> #
R> # The RADIUS request is normally cached internally for a short period
R> # of time, after the reply is sent to the NAS. The reply packet may be
R> # lost in the network, and the NAS will not see it. The NAS will then
R> # re-send the request, and the server will respond quickly with the
R> # cached reply.
R> #
R> # If this value is set too low, then duplicate requests from the NAS
R> # MAY NOT be detected, and will instead be handled as seperate requests.
R> #
R> # If this value is set too high, then the server will cache too many
R> # requests, and some new requests may get blocked. (See 'max_requests'.)
R> #
R> # Useful range of values: 2 to 10
R> #
R> cleanup_delay = 5
R> # max_requests: The maximum number of requests which the server keeps
R> # track of. This should be 256 multiplied by the number of clients.
R> # e.g. With 4 clients, this number should be 1024.
R> #
R> # If this number is too low, then when the server becomes busy,
R> # it will not respond to any new requests, until the 'cleanup_delay'
R> # time has passed, and it has removed the old requests.
R> #
R> # If this number is set too high, then the server will use a bit more
R> # memory for no real benefit.
R> #
R> # If you aren't sure what it should be set to, it's better to set it
R> # too high than too low. Setting it to 1000 per client is probably
R> # the highest it should be.
R> #
R> # Useful range of values: 256 to infinity
R> #
R> max_requests = 1024
R> # bind_address: Make the server listen on a particular IP address, and
R> # send replies out from that address. This directive is most useful
R> # for machines with multiple IP addresses on one interface.
R> #
R> # It can either contain "*", or an IP address, or a fully qualified
R> # Internet domain name. The default is "*"
R> #
R> bind_address = *
R> # port: Allows you to bind FreeRADIUS to a specific port.
R> #
R> # The default port that most NAS boxes use is 1645, which is historical.
R> # RFC 2138 defines 1812 to be the new port. Many new servers and
R> # NAS boxes use 1812, which can create interoperability problems.
R> #
R> # The port is defined here to be 0 so that the server will pick up
R> # the machine's local configuration for the radius port, as defined
R> # in /etc/services.
R> #
R> # If you want to use the default RADIUS port as defined on your server,
R> # (usually through 'grep radius /etc/services') set this to 0 (zero).
R> #
R> # A port given on the command-line via '-p' over-rides this one.
R> #
R> port = 0
R> # hostname_lookups: Log the names of clients or just their IP addresses
R> # e.g., www.freeradius.org (on) or 206.47.27.232 (off).
R> #
R> # The default is 'off' because it would be overall better for the net
R> # if people had to knowingly turn this feature on, since enabling it
R> # means that each client request will result in AT LEAST one lookup
R> # request to the nameserver. Enabling hostname_lookups will also
R> # mean that your server may stop randomly for 30 seconds from time
R> # to time, if the DNS requests take too long.
R> #
R> # Turning hostname lookups off also means that the server won't block
R> # for 30 seconds, if it sees an IP address which has no name associated
R> # with it.
R> #
R> # allowed values: {no, yes}
R> #
R> hostname_lookups = no
R> # Core dumps are a bad thing. This should only be set to 'yes'
R> # if you're debugging a problem with the server.
R> #
R> # allowed values: {no, yes}
R> #
R> allow_core_dumps = no
R> # Regular expressions
R> #
R> # These items are set at configure time. If they're set to "yes",
R> # then setting them to "no" turns off regular expression support.
R> #
R> # If they're set to "no" at configure time, then setting them to "yes"
R> # WILL NOT WORK. It will give you an error.
R> #
R> regular_expressions = yes
R> extended_expressions = yes
R> # Log the full User-Name attribute, as it was found in the request.
R> #
R> # allowed values: {no, yes}
R> #
R> log_stripped_names = no
R> # Log authentication requests to the log file.
R> #
R> # allowed values: {no, yes}
R> #
R> log_auth = yes
R> # Log passwords with the authentication requests.
R> # log_auth_badpass - logs password if it's rejected
R> # log_auth_goodpass - logs password if it's correct
R> #
R> # allowed values: {no, yes}
R> #
R> log_auth_badpass = yes
R> log_auth_goodpass = yes
R> # usercollide: Turn "username collision" code on and off. See the
R> # "doc/duplicate-users" file
R> #
R> usercollide = no
R> # lower_user / lower_pass:
R> # Lower case the username/password "before" or "after"
R> # attempting to authenticate.
R> #
R> # If "before", the server will first modify the request and then try
R> # to auth the user. If "after", the server will first auth using the
R> # values provided by the user. If that fails it will reprocess the
R> # request after modifying it as you specify below.
R> #
R> # This is as close as we can get to case insensitivity. It is the
R> # admin's job to ensure that the username on the auth db side is
R> # *also* lowercase to make this work
R> #
R> # Default is 'no' (don't lowercase values)
R> # Valid values = "before" / "after" / "no"
R> #
R> lower_user = no
R> lower_pass = no
R> # nospace_user / nospace_pass:
R> #
R> # Some users like to enter spaces in their username or password
R> # incorrectly. To save yourself the tech support call, you can
R> # eliminate those spaces here:
R> #
R> # Default is 'no' (don't remove spaces)
R> # Valid values = "before" / "after" / "no" (explanation above)
R> #
R> nospace_user = no
R> nospace_pass = no
R> # The program to execute to do concurrency checks.
R> checkrad = ${sbindir}/checkrad
R> # SECURITY CONFIGURATION
R> #
R> # There may be multiple methods of attacking on the server. This
R> # section holds the configuration items which minimize the impact
R> # of those attacks
R> #
R> security {
R> #
R> # max_attributes: The maximum number of attributes
R> # permitted in a RADIUS packet. Packets which have MORE
R> # than this number of attributes in them will be dropped.
R> #
R> # If this number is set too low, then no RADIUS packets
R> # will be accepted.
R> #
R> # If this number is set too high, then an attacker may be
R> # able to send a small number of packets which will cause
R> # the server to use all available memory on the machine.
R> #
R> # Setting this number to 0 means "allow any number of attributes"
R> max_attributes = 200
R> #
R> # delayed_reject: When sending an Access-Reject, it can be
R> # delayed for a few seconds. This may help slow down a DoS
R> # attack. It also helps to slow down people trying to brute-force
R> # crack a users password.
R> #
R> # Setting this number to 0 means "send rejects immediately"
R> #
R> # If this number is set higher than 'cleanup_delay', then the
R> # rejects will be sent at 'cleanup_delay' time, when the request
R> # is deleted from the internal cache of requests.
R> #
R> # Useful ranges: 1 to 5
R> reject_delay = 1
R> #
R> # status_server: Whether or not the server will respond
R> # to Status-Server requests.
R> #
R> # Normally this should be set to "no", because they're useless.
R> # See: http://www.freeradius.org/rfc/rfc2865.html#Keep-Alives
R> #
R> # However, certain NAS boxes may require them.
R> #
R> # When sent a Status-Server message, the server responds with
R> # and Access-Accept packet, containing a Reply-Message attribute,
R> # which is a string describing how long the server has been
R> # running.
R> #
R> status_server = no
R> }
R> # PROXY CONFIGURATION
R> #
R> # proxy_requests: Turns proxying of RADIUS requests on or off.
R> #
R> # The server has proxying turned on by default. If your system is NOT
R> # set up to proxy requests to another server, then you can turn proxying
R> # off here. This will save a small amount of resources on the server.
R> #
R> # If you have proxying turned off, and your configuration files say
R> # to proxy a request, then an error message will be logged.
R> #
R> # To disable proxying, change the "yes" to "no", and comment the
R> # $INCLUDE line.
R> #
R> # allowed values: {no, yes}
R> #
R> proxy_requests = yes
R> $INCLUDE ${confdir}/proxy.conf
R> # CLIENTS CONFIGURATION
R> #
R> # Client configuration is defined in "clients.conf".
R> #
R> # The 'clients.conf' file contains all of the information from the old
R> # 'clients' and 'naslist' configuration files. We recommend that you
R> # do NOT use 'client's or 'naslist', although they are still
R> # supported.
R> #
R> # Anything listed in 'clients.conf' will take precedence over the
R> # information from the old-style configuration files.
R> #
R> $INCLUDE ${confdir}/clients.conf
R> # SNMP CONFIGURATION
R> #
R> # Snmp configuration is only valid if SNMP support was enabled
R> # at compile time.
R> #
R> # To enable SNMP querying of the server, set the value of the
R> # 'snmp' attribute to 'yes'
R> #
R> snmp = no
R> $INCLUDE ${confdir}/snmp.conf
R> # THREAD POOL CONFIGURATION
R> #
R> # The thread pool is a long-lived group of threads which
R> # take turns (round-robin) handling any incoming requests.
R> #
R> # You probably want to have a few spare threads around,
R> # so that high-load situations can be handled immediately. If you
R> # don't have any spare threads, then the request handling will
R> # be delayed while a new thread is created, and added to the pool.
R> #
R> # You probably don't want too many spare threads around,
R> # otherwise they'll be sitting there taking up resources, and
R> # not doing anything productive.
R> #
R> # The numbers given below should be adequate for most situations.
R> #
R> thread pool {
R> # Number of servers to start initially --- should be a reasonable
R> # ballpark figure.
R> start_servers = 5
R> # Limit on the total number of servers running.
R> #
R> # If this limit is ever reached, clients will be LOCKED OUT, so it
R> # should NOT BE SET TOO LOW. It is intended mainly as a brake to
R> # keep a runaway server from taking the system with it as it spirals
R> # down...
R> #
R> # You may find that the server is regularly reaching the
R> # 'max_servers' number of threads, and that increasing
R> # 'max_servers' doesn't seem to make much difference.
R> #
R> # If this is the case, then the problem is MOST LIKELY that
R> # your back-end databases are taking too long to respond, and
R> # are preventing the server from responding in a timely manner.
R> #
R> # The solution is NOT do keep increasing the 'max_servers'
R> # value, but instead to fix the underlying cause of the
R> # problem: slow database, or 'hostname_lookups=yes'.
R> #
R> # For more information, see 'max_request_time', above.
R> #
R> max_servers = 32
R> # Server-pool size regulation. Rather than making you guess
R> # how many servers you need, FreeRADIUS dynamically adapts to
R> # the load it sees, that is, it tries to maintain enough
R> # servers to handle the current load, plus a few spare
R> # servers to handle transient load spikes.
R> #
R> # It does this by periodically checking how many servers are
R> # waiting for a request. If there are fewer than
R> # min_spare_servers, it creates a new spare. If there are
R> # more than max_spare_servers, some of the spares die off.
R> # The default values are probably OK for most sites.
R> #
R> min_spare_servers = 3
R> max_spare_servers = 10
R> # There may be memory leaks or resource allocation problems with
R> # the server. If so, set this value to 300 or so, so that the
R> # resources will be cleaned up periodically.
R> #
R> # This should only be necessary if there are serious bugs in the
R> # server which have not yet been fixed.
R> #
R> # '0' is a special value meaning 'infinity', or 'the servers never
R> # exit'
R> max_requests_per_server = 0
R> }
R> # MODULE CONFIGURATION
R> #
R> # The names and configuration of each module is located in this section.
R> #
R> # After the modules are defined here, they may be referred to by name,
R> # in other sections of this configuration file.
R> #
R> modules {
R> #
R> # Each module has a configuration as follows:
R> #
R> # name [ instance ] {
R> # config_item = value
R> # ...
R> # }
R> #
R> # The 'name' is used to load the 'rlm_name' library
R> # which implements the functionality of the module.
R> #
R> # The 'instance' is optional. To have two different instances
R> # of a module, it first must be referred to by 'name'.
R> # The different copies of the module are then created by
R> # inventing two 'instance' names, e.g. 'instance1' and 'instance2'
R> #
R> # The instance names can then be used in later configuration
R> # INSTEAD of the original 'name'. See the 'radutmp' configuration
R> # below for an example.
R> #
R> # PAP module to authenticate users based on their stored password
R> #
R> # Supports multiple encryption schemes
R> # clear: Clear text
R> # crypt: Unix crypt
R> # md5: MD5 ecnryption
R> # sha1: SHA1 encryption.
R> # DEFAULT: crypt
R> pap {
R> encryption_scheme = crypt
R> }
R> # CHAP module
R> #
R> # To authenticate requests containing a CHAP-Password attribute.
R> #
R> chap {
R> authtype = CHAP
R> }
R> # Pluggable Authentication Modules
R> #
R> # For Linux, see:
R> # http://www.kernel.org/pub/linux/libs/pam/index.html
R> #
R> pam {
R> #
R> # The name to use for PAM authentication.
R> # PAM looks in /etc/pam.d/${pam_auth_name}
R> # for it's configuration. See 'redhat/radiusd-pam'
R> # for a sample PAM configuration file.
R> #
R> # Note that any Pam-Auth attribute set in the 'authorize'
R> # section will over-ride this one.
R> #
R> pam_auth = radiusd
R> }
R> # Unix /etc/passwd style authentication
R> #
R> unix {
R> #
R> # Cache /etc/passwd, /etc/shadow, and /etc/group
R> #
R> # The default is to NOT cache them.
R> #
R> # For FreeBSD, you do NOT want to enable the cache,
R> # as it's password lookups are done via a database, so
R> # set this value to 'no'.
R> #
R> # Some systems (e.g. RedHat Linux with pam_pwbd) can
R> # take *seconds* to check a password, from a passwd
R> # file containing 1000's of entries. For those systems,
R> # you should set the cache value to 'yes', and set
R> # the locations of the 'passwd', 'shadow', and 'group'
R> # files, below.
R> #
R> # allowed values: {no, yes}
R> #cache = no
R> # Reload the cache every 600 seconds (10mins). 0 to disable.
R> #cache_reload = 600
R> #
R> # Define the locations of the normal passwd, shadow, and
R> # group files.
R> #
R> # 'shadow' is commented out by default, because not all
R> # systems have shadow passwords.
R> #
R> # To force the module to use the system password functions,
R> # instead of reading the files, leave the following entries
R> # commented out.
R> #
R> # This is required for some systems, like FreeBSD,
R> # and Mac OSX.
R> #
R> #passwd = /etc/passwd
R> #shadow = /etc/shadow
R> group = /etc/group
R> #
R> # Where the 'wtmp' file is located.
R> # This should be moved to it's own module soon.
R> #
R> # The only use for 'radlast'. If you don't use
R> # 'radlast', then you can comment out this item.
R> #
R> radwtmp = ${logdir}/radwtmp
R> }
R> # Extensible Authentication Protocol
R> #
R> # For all EAP related authentications
R> eap {
R> # Invoke the default supported EAP type when
R> # EAP-Identity response is received.
R> #
R> # The incoming EAP messages MAY NOT specify which EAP
R> # type they will be using, so it MUST be set here.
R> #
R> # For now, only one default EAP type may be used at a time.
R> #
R> default_eap_type = md5
R> # Default expiry time to clean the EAP list,
R> # It is maintained to correlate the
R> # EAP-response for each EAP-request sent.
R> timer_expire = 60
R> # Supported EAP-types
R> md5 {
R> }
R> # Cisco LEAP
R> #
R> # Cisco LEAP uses the MS-CHAP algorithm (but not
R> # the MS-CHAP attributes) to perform it's authentication.
R> #
R> # As a result, LEAP *requires* access to the plain-text
R> # User-Password, or the NT-Password attributes.
R> # 'System' authentication is impossible with LEAP.
R> #
R> leap {
R> }
R> ## EAP-TLS is highly experimental EAP-Type at the moment.
R> # Please give feedback on the mailing list.
R> #tls {
R> # private_key_password = password
R> # private_key_file = /path/filename
R> # If Private key & Certificate are located in the
R> # same file, then private_key_file & certificate_file
R> # must contain the same file name.
R> # certificate_file = /path/filename
R> # Trusted Root CA list
R> #CA_file = /path/filename
R> # dh_file = /path/filename
R> #random_file = /path/filename
R> #
R> # This can never exceed MAX_RADIUS_LEN (4096)
R> # preferably half the MAX_RADIUS_LEN, to
R> # accomodate other attributes in RADIUS packet.
R> # On most APs the MAX packet length is configured
R> # between 1500 - 1600. In these cases, fragment
R> # size should be <= 1024.
R> #
R> # fragment_size = 1024
R> # include_length is a flag which is by default set to yes
R> # If set to yes, Total Length of the message is included
R> # in EVERY packet we send.
R> # If set to no, Total Length of the message is included
R> # ONLY in the First packet of a fragment series.
R> #
R> # include_length = yes
R> #}
R> }
R> # Microsoft CHAP authentication
R> #
R> # This module supports MS-CHAP and MS-CHAPv2 authentication.
R> # It also enforces the SMB-Account-Ctrl attribute.
R> #
R> mschap {
R> #
R> # As of 0.9, the mschap module does NOT support
R> # reading from /etc/smbpasswd.
R> #
R> # If you are using /etc/smbpasswd, see the 'passwd'
R> # module for an example of how to use /etc/smbpasswd
R> # authtype value, if present, will be used
R> # to overwrite (or add) Auth-Type during
R> # authorization. Normally should be MS-CHAP
R> authtype = MS-CHAP
R> # if use_mppe is not set to no mschap will
R> # add MS-CHAP-MPPE-Keys for MS-CHAPv1 and
R> # MS-MPPE-Recv-Key/MS-MPPE-Send-Key for MS-CHAPv2
R> use_mppe = no
R> # if mppe is enabled require_encryption makes
R> # encryption moderate
R> require_encryption = no
R> # require_strong always requires 128 bit key
R> # encryption
R> require_strong = no
R> }
R> # Lightweight Directory Access Protocol (LDAP)
R> #
R> # This module definition allows you to use LDAP for
R> # authorization and authentication (Auth-Type := LDAP)
R> #
R> # See doc/rlm_ldap for description of configuration options
R> # and sample authorize{} and authenticate{} blocks
R> ldap {
R> server = "ldap.your.domain"
R> # identity = "cn=admin,o=My Org,c=UA"
R> # password = mypass
R> basedn = "o=My Org,c=UA"
R> filter = "(uid=%{Stripped-User-Name:-%{User-Name}})"
R> # set this to 'yes' to use TLS encrypted connections
R> # to the LDAP database by using the StartTLS extended
R> # operation.
R> # The StartTLS operation is supposed to be used with normal
R> # ldap connections instead of using ldaps (port 689) connections
R> start_tls = no
R> # default_profile = "cn=radprofile,ou=dialup,o=My Org,c=UA"
R> # profile_attribute = "radiusProfileDn"
R> access_attr = "dialupAccess"
R> # Mapping of RADIUS dictionary attributes to LDAP
R> # directory attributes.
R> dictionary_mapping = ${raddbdir}/ldap.attrmap
R> ldap_connections_number = 5
R> # password_header = "{clear}"
R> # password_attribute = userPassword
R> # groupname_attribute = cn
R> # groupmembership_filter =
R> "(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupO
R> fUniqueNames)(uniquemember=%{Ldap-UserDn})))"
R> # groupmembership_attribute = radiusGroupName
R> timeout = 4
R> timelimit = 3
R> net_timeout = 1
R> # compare_check_items = yes
R> # access_attr_used_for_allow = yes
R> }
R> # passwd module allows to do authorization via any passwd-like
R> # file and to extract any attributes from these modules
R> #
R> # parameters are:
R> # filename - path to filename
R> # format - format for filename record. This parameters
R> # correlates record in the passwd file and RADIUS
R> # attributes.
R> #
R> # Field marked as '*' is key field. That is, the parameter
R> # with this name from the request is used to search for
R> # the record from passwd file
R> # Attribute marked as '=' is added to reply_itmes instead
R> # of default configure_itmes
R> # Attribute marked as '~' is added to request_items
R> #
R> # Field marked as ',' may contain a comma separated list
R> # of attributes.
R> # authtype - if record found this Auth-Type is used to authenticate
R> # user
R> # hashsize - hashtable size. If 0 or not specified records are not
R> # stored in memory and file is red on every request.
R> # allowmultiplekeys - if few records for every key are allowed
R> # ignorenislike - ignore NIS-related records
R> # delimiter - symbol to use as a field separator in passwd file,
R> # for format ':' symbol is always used. '\0', '\n' are
R> # not allowed
R> #
R> # An example configuration for using /etc/smbpasswd.
R> #
R> passwd etc_smbpasswd {
R> filename = /usr/local/private/smbpasswd
R> format = "*User-Name::LM-Password:NT-Password:SMB-Account-CTRL-TEXT::"
R> authtype = MS-CHAP
R> hashsize = 100
R> ignorenislike = no
R> allowmultiplekeys = no
R> }
R> # Similar configuration, for the /etc/group file. Adds a Group-Name
R> # attribute for every group that the user is member of.
R> #
R> passwd etc_group {
R> filename = /etc/group
R> format = "=Group-Name:::*,User-Name"
R> hashsize = 50
R> ignorenislike = yes
R> allowmultiplekeys = yes
R> delimiter = ":"
R> }
R> # Realm module, for proxying.
R> #
R> # You can have multiple instances of the realm module to
R> # support multiple realm syntaxs at the same time. The
R> # search order is defined the order in the authorize and
R> # preacct blocks after the module config block.
R> #
R> # Two config options:
R> # format - must be 'prefix' or 'suffix'
R> # delimiter - must be a single character
R> # 'realm/username'
R> #
R> # Using this entry, IPASS users have their realm set to "IPASS".
R> realm realmslash {
R> format = prefix
R> delimiter = "/"
R> }
R> # '[EMAIL PROTECTED]'
R> #
R> realm suffix {
R> format = suffix
R> delimiter = "@"
R> }
R> # 'username%realm'
R> #
R> realm realmpercent {
R> format = suffix
R> delimiter = "%"
R> }
R> # rewrite arbitrary packets. Useful in accounting and authorization.
R> #
R> ## This module is highly experimental at the moment. Please give
R> ## feedback to the mailing list.
R> #
R> # The module can also use the Rewrite-Rule attribute. If it
R> # is set and matches the name of the module instance, then
R> # that module instance will be the only one which runs.
R> #
R> # Also if new_attribute is set to yes then a new attribute
R> # will be created containing the value replacewith and it
R> # will be added to searchin (packet, reply or config).
R> # searchfor,ignore_case and max_matches will be ignored in that case.
R> #
R> #attr_rewrite sanecallerid {
R> # attribute = Called-Station-Id
R> # may be "packet", "reply", or "config"
R> # searchin = packet
R> # searchfor = "[+ ]"
R> # replacewith = ""
R> # ignore_case = no
R> # new_attribute = no
R> # max_matches = 10
R> # ## If set to yes then the replace string will be appended to the original
R> string
R> # append = no
R> #}
R> # Preprocess the incoming RADIUS request, before handing it off
R> # to other modules.
R> #
R> # This module processes the 'huntgroups' and 'hints' files.
R> # In addition, it re-writes some weird attributes created
R> # by some NASes, and converts the attributes into a form which
R> # is a little more standard.
R> #
R> preprocess {
R> huntgroups = ${confdir}/huntgroups
R> hints = ${confdir}/hints
R> # This hack changes Ascend's wierd port numberings
R> # to standard 0-??? port numbers so that the "+" works
R> # for IP address assignments.
R> with_ascend_hack = no
R> ascend_channels_per_line = 23
R> # Windows NT machines often authenticate themselves as
R> # NT_DOMAIN\username
R> #
R> # If this is set to 'yes', then the NT_DOMAIN portion
R> # of the user-name is silently discarded.
R> with_ntdomain_hack = no
R> # Specialix Jetstream 8500 24 port access server.
R> #
R> # If the user name is 10 characters or longer, a "/"
R> # and the excess characters after the 10th are
R> # appended to the user name.
R> #
R> # If you're not running that NAS, you don't need
R> # this hack.
R> with_specialix_jetstream_hack = no
R> # Cisco sends it's VSA attributes with the attribute
R> # name *again* in the string, like:
R> #
R> # H323-Attribute = "h323-attribute=value".
R> #
R> # If this configuration item is set to 'yes', then
R> # the redundant data in the the attribute text is stripped
R> # out. The result is:
R> #
R> # H323-Attribute = "value"
R> #
R> # If you're not running a Cisco NAS, you don't need
R> # this hack.
R> with_cisco_vsa_hack = no
R> }
R> # Livingston-style 'users' file
R> #
R> files {
R> usersfile = ${confdir}/users
R> acctusersfile = ${confdir}/acct_users
R> # If you want to use the old Cistron 'users' file
R> # with FreeRADIUS, you should change the next line
R> # to 'compat = cistron'. You can the copy your 'users'
R> # file from Cistron.
R> compat = no
R> }
R> # Write a detailed log of all accounting records received.
R> #
R> detail {
R> # Note that we do NOT use NAS-IP-Address here, as
R> # that attribute MAY BE from the originating NAS, and
R> # NOT from the proxy which actually sent us the
R> # request. The Client-IP-Address attribute is ALWAYS
R> # the address of the client which sent us the
R> # request.
R> #
R> # The following line creates a new detail file for
R> # every radius client (by IP address or hostname).
R> # In addition, a new detail file is created every
R> # day, so that the detail file doesn't have to go
R> # through a 'log rotation'
R> #
R> # If your detail files are large, you may also want
R> # to add a ':%H' (see doc/variables.txt) to the end
R> # of it, to create a new detail file every hour, e.g.:
R> #
R> # ..../detail-%Y%m%d:%H
R> #
R> # This will create a new detail file for every hour.
R> #
R> detailfile = ${radacctdir}/%{Client-IP-Address}/detail-%Y%m%d
R> #
R> # The Unix-style permissions on the 'detail' file.
R> #
R> # The detail file often contains secret or private
R> # information about users. So by keeping the file
R> # permissions restrictive, we can prevent unwanted
R> # people from seeing that information.
R> detailperm = 0600
R> }
R> # Create a unique accounting session Id. Many NASes re-use or
R> # repeat values for Acct-Session-Id, causing no end of
R> # confusion.
R> #
R> # This module will add a (probably) unique session id
R> # to an accounting packet based on the attributes listed
R> # below found in the packet. See doc/rlm_acct_unique for
R> # more information.
R> #
R> acct_unique {
R> key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address,
R> NAS-Port-Id"
R> }
R> # Include another file that has the SQL-related configuration.
R> # This is another file only because it tends to be big.
R> #
R> # The following configuration file is for use with MySQL.
R> #
R> # For Postgresql, use: ${confdir}/postgresql.conf
R> # For MS-SQL, use: ${confdir}/mssql.conf
R> # For Oracle, use: ${confdir}/oraclesql.conf
R> #
R> $INCLUDE ${confdir}/sql.conf
R> # Write a 'utmp' style file, of which users are currently
R> # logged in, and where they've logged in from.
R> #
R> # This file is used mainly for Simultaneous-Use checking,
R> # and also 'radwho', to see who's currently logged in.
R> #
R> radutmp {
R> # Where the file is stored. It's not a log file,
R> # so it doesn't need rotating.
R> #
R> filename = ${logdir}/radutmp
R> # The field in the packet to key on for the
R> # 'user' name, If you have other fields which you want
R> # to use to key on to control Simultaneous-Use,
R> # then you can use them here.
R> #
R> # Note, however, that the size of the field in the
R> # 'utmp' data structure is small, around 32
R> # characters, so that will limit the possible choices
R> # of keys.
R> #
R> username = %{User-Name}
R> # Whether or not we want to treat "user" the same
R> # as "USER", or "User". Some systems have problems
R> # with case sensitivity, so this should be set to
R> # 'no' to enable the comparisons of the key attribute
R> # to be case insensitive.
R> #
R> case_sensitive = yes
R> # Accounting information may be lost, so the user MAY
R> # have logged off of the NAS, but we haven't noticed.
R> # If so, we can verify this information with the NAS,
R> #
R> # If we want to believe the 'utmp' file, then this
R> # configuration entry can be set to 'no'.
R> #
R> check_with_nas = yes
R> # Set the file permissions, as the contents of this file
R> # are usually private.
R> perm = 0600
R> callerid = "yes"
R> }
R> # "Safe" radutmp - does not contain caller ID, so it can be
R> # world-readable, and radwho can work for normal users, without
R> # exposing any information that isn't already exposed by who(1).
R> #
R> # This is another 'instance' of the radutmp module, but it is given
R> # then name "sradutmp" to identify it later in the "accounting"
R> # section.
R> radutmp sradutmp {
R> filename = ${logdir}/sradutmp
R> perm = 0644
R> callerid = "no"
R> }
R> # attr_filter - filters the attributes received in replies from
R> # proxied servers, to make sure we send back to our RADIUS client
R> # only allowed attributes.
R> attr_filter {
R> attrsfile = ${confdir}/attrs
R> }
R> # counter module:
R> # This module takes an attribute (count-attribute).
R> # It also takes a key, and creates a counter for each unique
R> # key. The count is incremented when accounting packets are
R> # received by the server. The value of the increment depends
R> # on the attribute type.
R> # If the attribute is Acct-Session-Time or of an integer type we add the
R> # value of the attribute. If it is anything else we increase the
R> # counter by one.
R> #
R> # The 'reset' parameter defines when the counters are all reset to
R> # zero. It can be hourly, daily, weekly, monthly or never.
R> #
R> # hourly: Reset on 00:00 of every hour
R> # daily: Reset on 00:00:00 every day
R> # weekly: Reset on 00:00:00 on sunday
R> # monthly: Reset on 00:00:00 of the first day of each month
R> #
R> # It can also be user defined. It should be of the form:
R> # num[hdwm] where:
R> # h: hours, d: days, w: weeks, m: months
R> # If the letter is ommited days will be assumed. In example:
R> # reset = 10h (reset every 10 hours)
R> # reset = 12 (reset every 12 days)
R> #
R> #
R> # The check-name attribute defines an attribute which will be
R> # registered by the counter module and can be used to set the
R> # maximum allowed value for the counter after which the user
R> # is rejected.
R> # Something like:
R> #
R> # DEFAULT Max-Daily-Session := 36000
R> # Fall-Through = 1
R> #
R> # You should add the counter module in the instantiate
R> # section so that it registers check-name before the files
R> # module reads the users file.
R> #
R> # If check-name is set and the user is to be rejected then we
R> # send back a Reply-Message and we log a Failure-Message in
R> # the radius.log
R> # If the count attribute is Acct-Session-Time then on each login
R> # we send back the remaining online time as a Session-Timeout attribute
R> #
R> # The counter-name can also be used instead of using the check-name
R> # like below:
R> #
R> # DEFAULT Daily-Session-Time > 3600, Auth-Type = Reject
R> # Reply-Message = "You've used up more than one hour today"
R> #
R> # The allowed-servicetype attribute can be used to only take
R> # into account specific sessions. For example if a user first
R> # logs in through a login menu and then selects ppp there will
R> # be two sessions. One for Login-User and one for Framed-User
R> # service type. We only need to take into account the second one.
R> #
R> # The module should be added in the instantiate, authorize and
R> # accounting sections. Make sure that in the authorize
R> # section it comes after any module which sets the
R> # 'check-name' attribute.
R> #
R> counter daily {
R> filename = ${raddbdir}/db.daily
R> key = User-Name
R> count-attribute = Acct-Session-Time
R> reset = daily
R> counter-name = Daily-Session-Time
R> check-name = Max-Daily-Session
R> allowed-servicetype = Framed-User
R> cache-size = 5000
R> }
R> # The "always" module is here for debugging purposes. Each
R> # instance simply returns the same result, always, without
R> # doing anything.
R> always fail {
R> rcode = fail
R> }
R> always reject {
R> rcode = reject
R> }
R> always ok {
R> rcode = ok
R> simulcount = 0
R> mpp = no
R> }
R> #
R> # The 'expression' module currently has no configuration.
R> expr {
R> }
R> #
R> # The 'digest' module currently has no configuration.
R> #
R> # "Digest" authentication against a Cisco SIP server.
R> # See 'doc/rfc/draft-sterman-aaa-sip-00.txt' for details
R> # on performing digest authentication for Cisco SIP servers.
R> #
R> digest {
R> }
R> #
R> # Execute external programs
R> #
R> # The first example is useful only for 'xlat'. To use it,
R> # put 'exec' into the 'instantiate' section. You can then
R> # do dynamic translation of attributes like:
R> #
R> # Attribute-Name = `{%exec:/path/to/program args}`
R> #
R> # The value of the attribute will be replaced with the output
R> # of the program which is executed. Due to RADIUS protocol
R> # limitations, any output over 253 bytes will be ignored.
R> #
R> # The RADIUS attributes from the user request will be placed
R> # into environment variables of the executed program, as
R> # described in 'doc/variables.txt'
R> #
R> exec {
R> wait = yes
R> input_pairs = request
R> }
R> #
R> # This is a more general example of the execute module.
R> #
R> # If you wish to execute an external program in more than
R> # one section (e.g. 'authorize', 'pre_proxy', etc), then it
R> # is probably best to define a different instance of the
R> # 'exec' module for every section.
R> #
R> exec echo {
R> #
R> # Wait for the program to finish.
R> #
R> # If we do NOT wait, then the program is "fire and
R> # forget", and any output attributes from it are ignored.
R> #
R> # If we are looking for the program to output
R> # attributes, and want to add those attributes to the
R> # request, then we MUST wait for the program to
R> # finish, and therefore set 'wait=yes'
R> #
R> # allowed values: {no, yes}
R> wait = yes
R> #
R> # The name of the program to execute, and it's
R> # arguments. Dynamic translation is done on this
R> # field, so things like the following example will
R> # work.
R> #
R> program = "/bin/echo %{User-Name}"
R> #
R> # The attributes which are placed into the
R> # environment variables for the program.
R> #
R> # Allowed values are:
R> #
R> # request attributes from the request
R> # reply attributes from the reply
R> # proxy-request attributes from the proxy request
R> # proxy-reply attributes from the proxy reply
R> #
R> # Note that some attributes may not exist at some
R> # stages. e.g. There may be no proxy-reply
R> # attributes if this module is used in the
R> # 'authorize' section.
R> #
R> input_pairs = request
R> #
R> # Where to place the output attributes (if any) from
R> # the executed program. The values allowed, and the
R> # restrictions as to availability, are the same as
R> # for the input_pairs.
R> #
R> output_pairs = reply
R> #
R> # When to execute the program. If the packet
R> # type does NOT match what's listed here, then
R> # the module does NOT execute the program.
R> #
R> # For a list of allowed packet types, see
R> # the 'dictionary' file, and look for VALUEs
R> # of the Packet-Type attribute.
R> #
R> # By default, the module executes on ANY packet.
R> # Un-comment out the following line to tell the
R> # module to execute only if an Access-Accept is
R> # being sent to the NAS.
R> #
R> #packet_type = Access-Accept
R> }
R> # Do server side ip pool management. Should be added in post-auth and
R> # accounting sections.
R> #
R> # The module also requires the existance of the Pool-Name
R> # attribute. That way the administrator can add the Pool-Name
R> # attribute in the user profiles and use different pools
R> # for different users. The Pool-Name attribute is a *check* item not
R> # a reply item.
R> #
R> # Example:
R> # radiusd.conf: ippool students { [...] }
R> # users file : DEFAULT Group == students, Pool-Name := "students"
R> #
R> # ********* IF YOU CHANGE THE RANGE PARAMETERS YOU MUST THEN ERASE THE DB
R> FILES *******
R> #
R> ippool main_pool {
R> # range-start,range-stop: The start and end ip
R> # addresses for the ip pool
R> range-start = 192.168.1.1
R> range-stop = 192.168.3.254
R> # netmask: The network mask used for the ip's
R> netmask = 255.255.255.0
R> # cache-size: The gdbm cache size for the db
R> # files. Should be equal to the number of ip's
R> # available in the ip pool
R> cache-size = 800
R> # session-db: The main db file used to allocate ip's to clients
R> session-db = ${raddbdir}/db.ippool
R> # ip-index: Helper db index file used in multilink
R> ip-index = ${raddbdir}/db.ipindex
R> # override: Will this ippool override a Framed-IP-Address already set
R> override = no
R> }
R> # ANSI X9.9 token support. Not included by default.
R> # $INCLUDE ${confdir}/x99.conf
R> }
R> # Instantiation
R> #
R> # This section orders the loading of the modules. Modules
R> # listed here will get loaded BEFORE the later sections like
R> # authorize, authenticate, etc. get examined.
R> #
R> # This section is not strictly needed. When a section like
R> # authorize refers to a module, it's automatically loaded and
R> # initialized. However, some modules may not be listed in any
R> # of the following sections, so they can be listed here.
R> #
R> # Also, listing modules here ensures that you have control over
R> # the order in which they are initalized. If one module needs
R> # something defined by another module, you can list them in order
R> # here, and ensure that the configuration will be OK.
R> #
R> instantiate {
R> #
R> # The expression module doesn't do authorization,
R> # authentication, or accounting. It only does dynamic
R> # translation, of the form:
R> #
R> # Session-Timeout = `%{expr:2 + 3}`
R> #
R> # So the module needs to be instantiated, but CANNOT be
R> # listed in any other section. See 'doc/rlm_expr' for
R> # more information.
R> #
R> expr
R> #
R> # We add the counter module here so that it registers
R> # the check-name attribute before any module which sets
R> # it
R> # daily
R> }
R> # Authorization. First preprocess (hints and huntgroups files),
R> # then realms, and finally look in the "users" file.
R> #
R> # The order of the realm modules will determine the order that
R> # we try to find a matching realm.
R> #
R> # Make *sure* that 'preprocess' comes before any realm if you
R> # need to setup hints for the remote radius server
R> authorize {
R> #
R> # The preprocess module takes care of sanitizing some bizarre
R> # attributes in the request, and turning them into attributes
R> # which are more standard.
R> #
R> # It takes care of processing the 'raddb/hints' and the
R> # 'raddb/huntgroups' files.
R> #
R> # It also adds a Client-IP-Address attribute to the request.
R> preprocess
R> #
R> # The chap module will set 'Auth-Type := CHAP' if we are
R> # handling a CHAP request and Auth-Type has not already been set
R> chap
R> # attr_filter
R> #
R> # This module takes care of EAP-MD5, EAP-TLS, and EAP-LEAP
R> # authentication.
R> eap
R> #
R> # If you have a Cisco SIP server authenticating against
R> # FreeRADIUS, uncomment the following line.
R> # digest
R> #
R> # Look for IPASS style 'realm/', and if not found, look for
R> # '@realm', and decide whether or not to proxy, based on
R> # that.
R> # realmslash
R> suffix
R> #
R> # Read the 'users' file
R> files
R> #
R> # If you are using /etc/smbpasswd, and are also doing
R> # mschap authentication, the un-comment this line, and
R> # configure the 'etc_smbpasswd' module, above.
R> etc_smbpasswd
R> #
R> # If the users are logging in with an MS-CHAP-Challenge
R> # attribute for authentication, the mschap module will find
R> # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP'
R> # to the request, which will cause the server to then use
R> # the mschap module for authentication.
R> mschap
R> # The ldap module will set Auth-Type to LDAP if it has not already been set
R> # ldap
R> # daily
R> }
R> # Authentication.
R> #
R> # This section lists which modules are available for authentication.
R> # Note that it does NOT mean 'try each module in order'. It means
R> # that you have to have a module from the 'authorize' section add
R> # a configuration attribute 'Auth-Type := FOO'. That authentication type
R> # is then used to pick the apropriate module from the list below.
R> #
R> # The default Auth-Type is Local. That is, whatever is not included inside
R> # an authtype section will be called only if Auth-Type is set to Local.
R> #
R> # So you should do the following:
R> # - Set Auth-Type to an appropriate value in the authorize modules above.
R> # For example, the chap module will set Auth-Type to CHAP, ldap to LDAP,
R> etc.
R> # - After that create corresponding authtype sections in the
R> # authenticate section below and call the appropriate modules.
R> authenticate {
R> #
R> # PAP authentication, when a back-end database listed
R> # in the 'authorize' section supplies a password. The
R> # password can be clear-text, or encrypted.
R> Auth-Type PAP {
R> pap
R> }
R> #
R> # Most people want CHAP authentication
R> # A back-end database listed in the 'authorize' section
R> # MUST supply a CLEAR TEXT password. Encrypted passwords
R> # won't work.
R> Auth-Type CHAP {
R> chap
R> }
R> #
R> # MSCHAP authentication.
R> Auth-Type MS-CHAP {
R> mschap
R> }
R> #
R> # If you have a Cisco SIP server authenticating against
R> # FreeRADIUS, uncomment the following line.
R> # digest
R> #
R> # Pluggable Authentication Modules.
R> # pam
R> #
R> # See 'man getpwent' for information on how the 'unix'
R> # module checks the users password. Note that packets
R> # containing CHAP-Password attributes CANNOT be authenticated
R> # against /etc/passwd! See the FAQ for details.
R> #
R> unix
R> # Uncomment it if you want to use ldap for authentication
R> # Auth-Type LDAP {
R> # ldap
R> # }
R> #
R> # Allow EAP authentication.
R> eap
R> }
R> #
R> # Pre-accounting. Decide which accounting type to use.
R> #
R> preacct {
R> preprocess
R> #
R> # Look for IPASS-style 'realm/', and if not found, look for
R> # '@realm', and decide whether or not to proxy, based on
R> # that.
R> #
R> # Accounting requests are generally proxied to the same
R> # home server as authentication requests.
R> # realmslash
R> suffix
R> #
R> # Read the 'acct_users' file
R> files
R> }
R> #
R> # Accounting. Log the accounting data.
R> #
R> accounting {
R> #
R> # Ensure that we have a semi-unique identifier for every
R> # request, and many NAS boxes are broken.
R> acct_unique
R> #
R> # Create a 'detail'ed log of the packets.
R> # Note that accounting requests which are proxied
R> # are also logged in the detail file.
R> detail
R> # daily
R> unix # wtmp file
R> #
R> # For Simultaneous-Use tracking.
R> #
R> # Due to packet losses in the network, the data here
R> # may be incorrect. There's little we can do about it.
R> radutmp
R> # sradutmp
R> # Return an address to the IP Pool when we see a stop record.
R> # main_pool
R> }
R> # Session database, used for checking Simultaneous-Use. Either the radutmp
R> # or rlm_sql module can handle this.
R> # The rlm_sql module is *much* faster
R> session {
R> radutmp
R> # sql
R> }
R> # Post-Authentication
R> # Once we KNOW that the user has been authenticated, there are
R> # additional steps we can take.
R> post-auth {
R> # Get an address from the IP Pool.
R> # main_pool
R> }
R> #
R> # When the server decides to proxy a request to a home server,
R> # the proxied request is first passed through the pre-proxy
R> # stage. This stage can re-write the request, or decide to
R> # cancel the proxy.
R> #
R> # Only a few modules currently have this method.
R> #
R> pre-proxy {
R> # attr_rewrite
R> }
R> #
R> # When the server receives a reply to a request it proxied
R> # to a home server, the request may be massaged here, in the
R> # post-proxy stage.
R> #
R> post-proxy {
R> # attr_rewrite
R> #
R> # If you are proxing LEAP, you MUST configure the EAP
R> # module, and you MUST list it here, in the post-proxy
R> # stage.
R> #
R> # You MUST also use the 'nostrip' option in the 'realm'
R> # configuration. Otherwise, the User-Name attribute
R> # in the proxied request will not match the user name
R> # hidden inside of the EAP packet, and the end server will
R> # reject the EAP request.
R> #
R> eap
R> }
R> Any help would be very welcome,
R> Thanks in advance,
R> Niels Piersma
R> -
R> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--
~/ZARAZA
Машина оказалась способной к единственному действию,
а именно умножению 2x2, да и то при этом ошибаясь. (Лем)
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
