6 # Create a unique accounting session Id. Many NASes re-use
7 # or repeat values for Acct-Session-Id, causing no end of
10 # This module will add a (probably) unique session id
11 # to an accounting packet based on the attributes listed
12 # below found in the packet. See doc/rlm_acct_unique for
16 key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port"
23 # The "always" module is here for debugging purposes. Each
24 # instance simply returns the same result, always, without
54 # This file defines a number of instances of the "attr_filter" module.
57 # attr_filter - filters the attributes received in replies from
58 # proxied servers, to make sure we send back to our RADIUS client
59 # only allowed attributes.
60 attr_filter attr_filter.post-proxy {
61 attrsfile = ${confdir}/attrs
64 # attr_filter - filters the attributes in the packets we send to
65 # the RADIUS home servers.
66 attr_filter attr_filter.pre-proxy {
67 attrsfile = ${confdir}/attrs.pre-proxy
70 # Enforce RFC requirements on the contents of Access-Reject
71 # packets. See the comments at the top of the file for
74 attr_filter attr_filter.access_reject {
76 attrsfile = ${confdir}/attrs.access_reject
79 # Enforce RFC requirements on the contents of the
80 # Accounting-Response packets. See the comments at the
81 # top of the file for more details.
83 attr_filter attr_filter.accounting_response {
85 attrsfile = ${confdir}/attrs.accounting_response
91 # rewrite arbitrary packets. Useful in accounting and authorization.
93 # As of 2.0, much of the functionality of this module is in "unlang".
94 # You should probably investigate using that before trying to use
95 # the "attr_rewrite" module.
98 # The module can also use the Rewrite-Rule attribute. If it
99 # is set and matches the name of the module instance, then
100 # that module instance will be the only one which runs.
102 # Also if new_attribute is set to yes then a new attribute
103 # will be created containing the value replacewith and it
104 # will be added to searchin (packet, reply, proxy,
105 # proxy_reply or config).
107 # searchfor,ignore_case and max_matches will be ignored in that case.
109 # Backreferences are supported.
110 # %{0} will contain the string the whole match
111 # %{1} to %{8} will contain the contents of the 1st to
112 # the 8th parentheses
114 # If max_matches is greater than one, the backreferences will
115 # correspond to the first attributed that matched.
118 attr_rewrite sanecallerid {
119 attribute = Called-Station-Id
120 # may be "packet", "reply", "proxy", "proxy_reply" or "config"
128 ## If set to yes then the replace string will be
129 ## appended to the original string
139 # To authenticate requests containing a CHAP-Password attribute.
148 # A simple value checking module
150 # As of 2.0, much of the functionality of this module is in "unlang".
151 # You should probably investigate using that before trying to use
152 # the "checkval" module.
154 # It can be used to check if an attribute value in the request
155 # matches a (possibly multi valued) attribute in the check
156 # items This can be used for example for caller-id
157 # authentication. For the module to run, both the request
158 # attribute and the check items attribute must exist
161 # A user has an ldap entry with 2 radiusCallingStationId
162 # attributes with values "12345678" and "12345679". If we
163 # enable rlm_checkval, then any request which contains a
164 # Calling-Station-Id with one of those two values will be
165 # accepted. Requests with other values for
166 # Calling-Station-Id will be rejected.
168 # Regular expressions in the check attribute value are allowed
169 # as long as the operator is '=~'
172 # The attribute to look for in the request
173 item-name = Calling-Station-Id
175 # The attribute to look for in check items. Can be multi valued
176 check-name = Calling-Station-Id
178 # The data type. Can be
179 # string,integer,ipaddr,date,abinary,octets
182 # If set to yes and we dont find the item-name attribute in the
183 # request then we send back a reject
185 #notfound-reject = no
193 # This module takes an attribute (count-attribute).
194 # It also takes a key, and creates a counter for each unique
195 # key. The count is incremented when accounting packets are
196 # received by the server. The value of the increment depends
197 # on the attribute type.
198 # If the attribute is Acct-Session-Time or of an integer type we add
199 # the value of the attribute. If it is anything else we increase the
202 # The 'reset' parameter defines when the counters are all reset to
203 # zero. It can be hourly, daily, weekly, monthly or never.
205 # hourly: Reset on 00:00 of every hour
206 # daily: Reset on 00:00:00 every day
207 # weekly: Reset on 00:00:00 on sunday
208 # monthly: Reset on 00:00:00 of the first day of each month
210 # It can also be user defined. It should be of the form:
212 # h: hours, d: days, w: weeks, m: months
213 # If the letter is ommited days will be assumed. In example:
214 # reset = 10h (reset every 10 hours)
215 # reset = 12 (reset every 12 days)
218 # The check-name attribute defines an attribute which will be
219 # registered by the counter module and can be used to set the
220 # maximum allowed value for the counter after which the user
224 # DEFAULT Max-Daily-Session := 36000
227 # You should add the counter module in the instantiate
228 # section so that it registers check-name before the files
229 # module reads the users file.
231 # If check-name is set and the user is to be rejected then we
232 # send back a Reply-Message and we log a Failure-Message in
235 # If the count attribute is Acct-Session-Time then on each
236 # login we send back the remaining online time as a
237 # Session-Timeout attribute ELSE and if the reply-name is
238 # set, we send back that attribute. The reply-name attribute
239 # MUST be of an integer type.
241 # The counter-name can also be used instead of using the check-name
244 # DEFAULT Daily-Session-Time > 3600, Auth-Type = Reject
245 # Reply-Message = "You've used up more than one hour today"
247 # The allowed-servicetype attribute can be used to only take
248 # into account specific sessions. For example if a user first
249 # logs in through a login menu and then selects ppp there will
250 # be two sessions. One for Login-User and one for Framed-User
251 # service type. We only need to take into account the second one.
253 # The module should be added in the instantiate, authorize and
254 # accounting sections. Make sure that in the authorize
255 # section it comes after any module which sets the
256 # 'check-name' attribute.
259 filename = ${db_dir}/db.daily
261 count-attribute = Acct-Session-Time
263 counter-name = Daily-Session-Time
264 check-name = Max-Daily-Session
265 reply-name = Session-Timeout
266 allowed-servicetype = Framed-User
274 # Write a detailed log of all accounting records received.
277 # Note that we do NOT use NAS-IP-Address here, as
278 # that attribute MAY BE from the originating NAS, and
279 # NOT from the proxy which actually sent us the
280 # request. The Client-IP-Address attribute is ALWAYS
281 # the address of the client which sent us the
284 # The following line creates a new detail file for
285 # every radius client (by IP address or hostname).
286 # In addition, a new detail file is created every
287 # day, so that the detail file doesn't have to go
288 # through a 'log rotation'
290 # If your detail files are large, you may also want
291 # to add a ':%H' (see doc/variables.txt) to the end
292 # of it, to create a new detail file every hour, e.g.:
294 # ..../detail-%Y%m%d:%H
296 # This will create a new detail file for every hour.
298 detailfile = ${radacctdir}/%{Client-IP-Address}/detail-%Y%m%d
301 # The Unix-style permissions on the 'detail' file.
303 # The detail file often contains secret or private
304 # information about users. So by keeping the file
305 # permissions restrictive, we can prevent unwanted
306 # people from seeing that information.
310 # Every entry in the detail file has a header which
311 # is a timestamp. By default, we use the ctime
312 # format (see "man ctime" for details).
314 # The header can be customized by editing this
315 # string. See "doc/variables.txt" for a description
316 # of what can be put here.
321 # Certain attributes such as User-Password may be
322 # "sensitive", so they should not be printed in the
323 # detail file. This section lists the attributes
324 # that should be suppressed.
326 # The attributes should be listed one to a line.
335 # Detail file writer, used in the following examples:
337 # raddb/sites-available/robust-proxy-accounting
338 # raddb/sites-available/decoupled-accounting
340 # Note that this module can write detail files that are read by
341 # only ONE "listen" section. If you use BOTH of the examples
342 # above, you will need to define TWO "detail" modules.
344 # e.g. detail1.example.com && detail2.example.com
347 # We write *multiple* detail files here. They will be processed by
348 # the detail "listen" section in the order that they were created.
349 # The directory containing these files should NOT be used for any
350 # other purposes. i.e. It should have NO other files in it.
352 # Writing multiple detail enables the server to process the pieces
353 # in smaller chunks. This helps in certain catastrophic corner cases.
357 detail detail.example.com {
358 detailfile = ${radacctdir}/detail.example.com/detail-%Y%m%d:%H
365 # More examples of doing detail logs.
368 # Many people want to log authentication requests.
369 # Rather than modifying the server core to print out more
370 # messages, we can use a different instance of the 'detail'
371 # module, to log the authentication requests to a file.
373 # You will also need to un-comment the 'auth_log' line
374 # in the 'authorize' section, below.
377 detailfile = ${radacctdir}/%{Client-IP-Address}/auth-detail-%Y%m%d
380 # This MUST be 0600, otherwise anyone can read
381 # the users passwords!
384 # You may also strip out passwords completely
391 # This module logs authentication reply packets sent
392 # to a NAS. Both Access-Accept and Access-Reject packets
395 # You will also need to un-comment the 'reply_log' line
396 # in the 'post-auth' section, below.
399 detailfile = ${radacctdir}/%{Client-IP-Address}/reply-detail-%Y%m%d
405 # This module logs packets proxied to a home server.
407 # You will also need to un-comment the 'pre_proxy_log' line
408 # in the 'pre-proxy' section, below.
410 detail pre_proxy_log {
411 detailfile = ${radacctdir}/%{Client-IP-Address}/pre-proxy-detail-%Y%m%d
414 # This MUST be 0600, otherwise anyone can read
415 # the users passwords!
418 # You may also strip out passwords completely
425 # This module logs response packets from a home server.
427 # You will also need to un-comment the 'post_proxy_log' line
428 # in the 'post-proxy' section, below.
430 detail post_proxy_log {
431 detailfile = ${radacctdir}/%{Client-IP-Address}/post-proxy-detail-%Y%m%d
440 # The 'digest' module currently has no configuration.
442 # "Digest" authentication against a Cisco SIP server.
443 # See 'doc/rfc/draft-sterman-aaa-sip-00.txt' for details
444 # on performing digest authentication for Cisco SIP servers.
453 # This is a more general example of the execute module.
455 # This one is called "echo".
457 # Attribute-Name = `%{echo:/path/to/program args}`
459 # If you wish to execute an external program in more than
460 # one section (e.g. 'authorize', 'pre_proxy', etc), then it
461 # is probably best to define a different instance of the
462 # 'exec' module for every section.
464 # The return value of the program run determines the result
465 # of the exec instance call as follows:
466 # (See doc/configurable_failover for details)
468 # < 0 : fail the module failed
469 # = 0 : ok the module succeeded
470 # = 1 : reject the module rejected the user
471 # = 2 : fail the module failed
472 # = 3 : ok the module succeeded
473 # = 4 : handled the module has done everything to handle the request
474 # = 5 : invalid the user's configuration entry was invalid
475 # = 6 : userlock the user was locked out
476 # = 7 : notfound the user was not found
477 # = 8 : noop the module did nothing
478 # = 9 : updated the module updated information in the request
479 # > 9 : fail the module failed
483 # Wait for the program to finish.
485 # If we do NOT wait, then the program is "fire and
486 # forget", and any output attributes from it are ignored.
488 # If we are looking for the program to output
489 # attributes, and want to add those attributes to the
490 # request, then we MUST wait for the program to
491 # finish, and therefore set 'wait=yes'
493 # allowed values: {no, yes}
497 # The name of the program to execute, and it's
498 # arguments. Dynamic translation is done on this
499 # field, so things like the following example will
502 program = "/bin/echo %{User-Name}"
505 # The attributes which are placed into the
506 # environment variables for the program.
508 # Allowed values are:
510 # request attributes from the request
511 # config attributes from the configuration items list
512 # reply attributes from the reply
513 # proxy-request attributes from the proxy request
514 # proxy-reply attributes from the proxy reply
516 # Note that some attributes may not exist at some
517 # stages. e.g. There may be no proxy-reply
518 # attributes if this module is used in the
519 # 'authorize' section.
521 input_pairs = request
524 # Where to place the output attributes (if any) from
525 # the executed program. The values allowed, and the
526 # restrictions as to availability, are the same as
527 # for the input_pairs.
532 # When to execute the program. If the packet
533 # type does NOT match what's listed here, then
534 # the module does NOT execute the program.
536 # For a list of allowed packet types, see
537 # the 'dictionary' file, and look for VALUEs
538 # of the Packet-Type attribute.
540 # By default, the module executes on ANY packet.
541 # Un-comment out the following line to tell the
542 # module to execute only if an Access-Accept is
543 # being sent to the NAS.
545 #packet_type = Access-Accept
548 # Should we escape the environment variables?
550 # If this is set, all the RADIUS attributes
551 # are capitalised and dashes replaced with
552 # underscores. Also, RADIUS values are surrounded
553 # with double-quotes.
555 # That is to say: User-Name=BobUser => USER_NAME="BobUser"
563 # "passwd" configuration, for the /etc/group file. Adds a Etc-Group-Name
564 # attribute for every group that the user is member of.
566 # You will have to define the Etc-Group-Name in the 'dictionary' file
567 # as a 'string' type.
569 # The Group-Name attribute is automatically created by the Unix module,
570 # and does checking against /etc/group automatically.
572 # i.e. this module should NOT be used as-is, but should be edited to
573 # point to a different group file.
576 filename = /etc/group
577 format = "=Etc-Group-Name:::*,User-Name"
580 allowmultiplekeys = yes
589 # Execute external programs
591 # This module is useful only for 'xlat'. To use it,
592 # put 'exec' into the 'instantiate' section. You can then
593 # do dynamic translation of attributes like:
595 # Attribute-Name = `%{exec:/path/to/program args}`
597 # The value of the attribute will be replaced with the output
598 # of the program which is executed. Due to RADIUS protocol
599 # limitations, any output over 253 bytes will be ignored.
601 # The RADIUS attributes from the user request will be placed
602 # into environment variables of the executed program, as
603 # described in "man unlang" and in doc/variables.txt
605 # See also "echo" for more sample configuration.
609 input_pairs = request
618 # The expiration module. This handles the Expiration attribute
619 # It should be included in the *end* of the authorize section
620 # in order to handle user Expiration. It should also be included
621 # in the instantiate section in order to register the Expiration
626 # The Reply-Message which will be sent back in case the
627 # account has expired. Dynamic substitution is supported
629 reply-message = "Password Has Expired\r\n"
630 #reply-message = "Your account has expired, %{User-Name}\r\n"
637 # The 'expression' module currently has no configuration.
639 # This module is useful only for 'xlat'. To use it,
640 # put 'expr' into the 'instantiate' section. You can then
641 # do dynamic translation of attributes like:
643 # Attribute-Name = `%{expr:2 + 3 + %{exec: uid -u}}`
645 # The value of the attribute will be replaced with the output
646 # of the program which is executed. Due to RADIUS protocol
647 # limitations, any output over 253 bytes will be ignored.
649 # The module also registers a few paircompare functions
656 # Livingston-style 'users' file
659 # The default key attribute to use for matches. The content
660 # of this attribute is used to match the "name" of the
662 #key = "%{Stripped-User-Name:-%{User-Name}}"
664 usersfile = ${confdir}/users
665 acctusersfile = ${confdir}/acct_users
666 preproxy_usersfile = ${confdir}/preproxy_users
668 # If you want to use the old Cistron 'users' file
669 # with FreeRADIUS, you should change the next line
670 # to 'compat = cistron'. You can the copy your 'users'
678 # Do server side ip pool management. Should be added in
679 # post-auth and accounting sections.
681 # The module also requires the existance of the Pool-Name
682 # attribute. That way the administrator can add the Pool-Name
683 # attribute in the user profiles and use different pools for
684 # different users. The Pool-Name attribute is a *check* item
687 # The Pool-Name should be set to the ippool module instance
688 # name or to DEFAULT to match any module.
692 # radiusd.conf: ippool students { [...] }
693 # ippool teachers { [...] }
694 # users file : DEFAULT Group == students, Pool-Name := "students"
695 # DEFAULT Group == teachers, Pool-Name := "teachers"
696 # DEFAULT Group == other, Pool-Name := "DEFAULT"
698 # ********* IF YOU CHANGE THE RANGE PARAMETERS YOU MUST *********
699 # ********* THEN ERASE THE DB FILES *********
703 # range-start,range-stop:
704 # The start and end ip addresses for this pool.
705 range-start = 192.168.1.1
706 range-stop = 192.168.3.254
709 # The network mask used for this pool.
710 netmask = 255.255.255.0
713 # The gdbm cache size for the db files. Should
714 # be equal to the number of ip's available in
719 # The main db file used to allocate addresses.
720 session-db = ${db_dir}/db.ippool
723 # Helper db index file used in multilink
724 ip-index = ${db_dir}/db.ipindex
727 # If set, the Framed-IP-Address already in the
728 # reply (if any) will be discarded, and replaced
729 # with a Framed-IP-Address assigned here.
733 # Specifies the maximum time in seconds that an
734 # entry may be active. If set to zero, means
735 # "no timeout". The default value is 0
739 # The key to use for the session database (which
740 # holds the allocated ip's) normally it should
741 # just be the nas ip/port (which is the default).
743 # If your NAS sends the same value of NAS-Port
744 # all requests, the key should be based on some
745 # other attribute that is in ALL requests, AND
746 # is unique to each machine needing an IP address.
747 #key = "%{NAS-IP-Address} %{NAS-Port}"
754 # Kerberos. See doc/rlm_krb5 for minimal docs.
757 keytab = /path/to/keytab
758 service_principal = name_of_principle
764 # Lightweight Directory Access Protocol (LDAP)
766 # This module definition allows you to use LDAP for
767 # authorization and authentication.
769 # See raddb/sites-available/default for reference to the
770 # ldap module in the authorize and authenticate sections.
772 # However, LDAP can be used for authentication ONLY when the
773 # Access-Request packet contains a clear-text User-Password
774 # attribute. LDAP authentication will NOT work for any other
775 # authentication method.
777 # This means that LDAP servers don't understand EAP. If you
778 # force "Auth-Type = LDAP", and then send the server a
779 # request containing EAP authentication, then authentication
782 # The solution is to use the default configuration, which does
785 # Setting "Auth-Type = LDAP" is ALMOST ALWAYS WRONG. We
786 # really can't emphasize this enough.
790 # Note that this needs to match the name in the LDAP
791 # server certificate, if you're using ldaps.
792 server = "ldap.your.domain"
793 #identity = "cn=admin,o=My Org,c=UA"
795 basedn = "o=My Org,c=UA"
796 filter = "(uid=%{Stripped-User-Name:-%{User-Name}})"
797 #base_filter = "(objectclass=radiusprofile)"
799 # How many connections to keep open to the LDAP server.
800 # This saves time over opening a new LDAP socket for
801 # every authentication request.
802 ldap_connections_number = 5
804 # seconds to wait for LDAP query to finish. default: 20
807 # seconds LDAP server has to process the query (server-side
808 # time limit). default: 20
810 # LDAP_OPT_TIMELIMIT is set to this value.
814 # seconds to wait for response of the server. (network
815 # failures) default: 10
817 # LDAP_OPT_NETWORK_TIMEOUT is set to this value.
821 # This subsection configures the tls related items
822 # that control how FreeRADIUS connects to an LDAP
823 # server. It contains all of the "tls_*" configuration
824 # entries used in older versions of FreeRADIUS. Those
825 # configuration entries can still be used, but we recommend
829 # Set this to 'yes' to use TLS encrypted connections
830 # to the LDAP database by using the StartTLS extended
833 # The StartTLS operation is supposed to be
834 # used with normal ldap connections instead of
835 # using ldaps (port 689) connections
838 # cacertfile = /path/to/cacert.pem
839 # cacertdir = /path/to/ca/dir/
840 # certfile = /path/to/radius.crt
841 # keyfile = /path/to/radius.key
842 # randfile = /path/to/rnd
844 # Certificate Verification requirements. Can be:
845 # "never" (don't even bother trying)
846 # "allow" (try, but don't fail if the cerificate
848 # "demand" (fail if the certificate doesn't verify.)
850 # The default is "allow"
851 # require_cert = "demand"
854 # default_profile = "cn=radprofile,ou=dialup,o=My Org,c=UA"
855 # profile_attribute = "radiusProfileDn"
856 # access_attr = "dialupAccess"
858 # Mapping of RADIUS dictionary attributes to LDAP
859 # directory attributes.
860 dictionary_mapping = ${confdir}/ldap.attrmap
862 # Set password_attribute = nspmPassword to get the
863 # user's password from a Novell eDirectory
864 # backend. This will work ONLY IF FreeRADIUS has been
865 # built with the --with-edir configure option.
867 # See also the following links:
869 # http://www.novell.com/coolsolutions/appnote/16745.html
870 # https://secure-support.novell.com/KanisaPlatform/Publishing/558/3009668_f.SAL_Public.html
872 # Novell may require TLS encrypted sessions before returning
873 # the user's password.
875 # password_attribute = userPassword
877 # Un-comment the following to disable Novell
878 # eDirectory account policy check and intruder
879 # detection. This will work *only if* FreeRADIUS is
880 # configured to build with --with-edir option.
882 edir_account_policy_check = no
885 # Group membership checking. Disabled by default.
887 # groupname_attribute = cn
888 # groupmembership_filter = "(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=GroupOfUniqueNames)(uniquemember=%{Ldap-UserDn})))"
889 # groupmembership_attribute = radiusGroupName
891 # compare_check_items = yes
893 # access_attr_used_for_allow = yes
896 # By default, if the packet contains a User-Password,
897 # and no other module is configured to handle the
898 # authentication, the LDAP module sets itself to do
899 # LDAP bind for authentication.
901 # THIS WILL ONLY WORK FOR PAP AUTHENTICATION.
903 # THIS WILL NOT WORK FOR CHAP, MS-CHAP, or 802.1x (EAP).
905 # You can disable this behavior by setting the following
906 # configuration entry to "no".
908 # allowed values: {no, yes}
909 # set_auth_type = yes
911 # ldap_debug: debug flag for LDAP SDK
912 # (see OpenLDAP documentation). Set this to enable
913 # huge amounts of LDAP debugging on the screen.
914 # You should only use this if you are an LDAP expert.
916 # default: 0x0000 (no debugging messages)
917 # Example:(LDAP_DEBUG_FILTER+LDAP_DEBUG_CONNS)
924 # The logintime module. This handles the Login-Time,
925 # Current-Time, and Time-Of-Day attributes. It should be
926 # included in the *end* of the authorize section in order to
927 # handle Login-Time checks. It should also be included in the
928 # instantiate section in order to register the Current-Time
929 # and Time-Of-Day comparison functions.
931 # When the Login-Time attribute is set to some value, and the
932 # user has bene permitted to log in, a Session-Timeout is
933 # calculated based on the remaining time. See "doc/README".
937 # The Reply-Message which will be sent back in case
938 # the account is calling outside of the allowed
939 # timespan. Dynamic substitution is supported.
941 reply-message = "You are calling outside your allowed timespan\r\n"
942 #reply-message = "Outside allowed timespan (%{control:Login-Time}), %{User-Name}\r\n"
944 # The minimum timeout (in seconds) a user is allowed
945 # to have. If the calculated timeout is lower we don't
946 # allow the logon. Some NASes do not handle values
947 # lower than 60 seconds well.
955 ######################################################################
957 # This next section is a sample configuration for the "passwd"
958 # module, that reads flat-text files.
960 # The file is in the format <mac>,<ip>
962 # 00:01:02:03:04:05,192.168.1.100
963 # 01:01:02:03:04:05,192.168.1.101
964 # 02:01:02:03:04:05,192.168.1.102
966 # This lets you perform simple static IP assignments from a flat-text
967 # file. You will have to define lease times yourself.
969 ######################################################################
972 filename = ${confdir}/mac2ip
973 format = "*DHCP-Client-Hardware-Address:=DHCP-Your-IP-Address"
980 # A simple file to map a MAC address to a VLAN.
982 # The file should be in the format MAC,VLAN
983 # the VLAN name cannot have spaces in it, for example:
985 # 00:01:02:03:04:05,VLAN1
986 # 03:04:05:06:07:08,VLAN2
990 filename = ${confdir}/mac2vlan
991 format = "*VMPS-Mac:=VMPS-VLAN-Name"
998 # Microsoft CHAP authentication
1000 # This module supports MS-CHAP and MS-CHAPv2 authentication.
1001 # It also enforces the SMB-Account-Ctrl attribute.
1005 # If you are using /etc/smbpasswd, see the 'passwd'
1006 # module for an example of how to use /etc/smbpasswd
1008 # if use_mppe is not set to no mschap will
1009 # add MS-CHAP-MPPE-Keys for MS-CHAPv1 and
1010 # MS-MPPE-Recv-Key/MS-MPPE-Send-Key for MS-CHAPv2
1014 # if mppe is enabled require_encryption makes
1015 # encryption moderate
1017 #require_encryption = yes
1019 # require_strong always requires 128 bit key
1022 #require_strong = yes
1024 # Windows sends us a username in the form of
1025 # DOMAIN\user, but sends the challenge response
1026 # based on only the user portion. This hack
1027 # corrects for that incorrect behavior.
1029 #with_ntdomain_hack = no
1031 # The module can perform authentication itself, OR
1032 # use a Windows Domain Controller. This configuration
1033 # directive tells the module to call the ntlm_auth
1034 # program, which will do the authentication, and return
1035 # the NT-Key. Note that you MUST have "winbindd" and
1036 # "nmbd" running on the local machine for ntlm_auth
1037 # to work. See the ntlm_auth program documentation
1040 # If ntlm_auth is configured below, then the mschap
1041 # module will call ntlm_auth for every MS-CHAP
1042 # authentication request. If there is a cleartext
1043 # or NT hashed password available, you can set
1044 # "MS-CHAP-Use-NTLM-Auth := No" in the control items,
1045 # and the mschap module will do the authentication itself,
1046 # without calling ntlm_auth.
1048 # Be VERY careful when editing the following line!
1050 # You can also try setting the user name as:
1052 # ... --username=%{mschap:User-Name} ...
1054 # In that case, the mschap module will look at the User-Name
1055 # attribute, and do prefix/suffix checks in order to obtain
1056 # the "best" user name for the request.
1058 #ntlm_auth = "/path/to/ntlm_auth --request-nt-key --username=%{Stripped-User-Name:-%{User-Name:-None}} --challenge=%{mschap:Challenge:-00} --nt-response=%{mschap:NT-Response:-00}"
1065 # Pluggable Authentication Modules
1068 # http://www.kernel.org/pub/linux/libs/pam/index.html
1070 # WARNING: On many systems, the system PAM libraries have
1071 # memory leaks! We STRONGLY SUGGEST that you do not
1072 # use PAM for authentication, due to those memory leaks.
1076 # The name to use for PAM authentication.
1077 # PAM looks in /etc/pam.d/${pam_auth_name}
1078 # for it's configuration. See 'redhat/radiusd-pam'
1079 # for a sample PAM configuration file.
1081 # Note that any Pam-Auth attribute set in the 'authorize'
1082 # section will over-ride this one.
1090 # PAP module to authenticate users based on their stored password
1092 # Supports multiple encryption/hash schemes. See "man rlm_pap"
1095 # The "auto_header" configuration item can be set to "yes".
1096 # In this case, the module will look inside of the User-Password
1097 # attribute for the headers {crypt}, {clear}, etc., and will
1098 # automatically create the attribute on the right-hand side,
1099 # with the correct value. It will also automatically handle
1100 # Base-64 encoded data, hex strings, and binary data.
1108 # passwd module allows to do authorization via any passwd-like
1109 # file and to extract any attributes from these modules
1112 # filename - path to filename
1113 # format - format for filename record. This parameters
1114 # correlates record in the passwd file and RADIUS
1117 # Field marked as '*' is key field. That is, the parameter
1118 # with this name from the request is used to search for
1119 # the record from passwd file
1120 # Attribute marked as '=' is added to reply_itmes instead
1121 # of default configure_itmes
1122 # Attribute marked as '~' is added to request_items
1124 # Field marked as ',' may contain a comma separated list
1126 # hashsize - hashtable size. If 0 or not specified records are not
1127 # stored in memory and file is red on every request.
1128 # allowmultiplekeys - if few records for every key are allowed
1129 # ignorenislike - ignore NIS-related records
1130 # delimiter - symbol to use as a field separator in passwd file,
1131 # for format ':' symbol is always used. '\0', '\n' are
1140 # Module implementing a DIFFERENT policy language.
1141 # The syntax here is NOT "unlang", but something else.
1143 # See the "raddb/policy.txt" file for documentation and examples.
1144 # There isn't much else in the way of documentation, sorry.
1147 # The only configuration item is a filename containing
1148 # the policies to execute.
1150 # When "policy" is listed in a section (e.g. "authorize"),
1151 # it will run a policy named for that section.
1153 filename = ${confdir}/policy.txt
1160 # Preprocess the incoming RADIUS request, before handing it off
1163 # This module processes the 'huntgroups' and 'hints' files.
1164 # In addition, it re-writes some weird attributes created
1165 # by some NASes, and converts the attributes into a form which
1166 # is a little more standard.
1169 huntgroups = ${confdir}/huntgroups
1170 hints = ${confdir}/hints
1172 # This hack changes Ascend's wierd port numberings
1173 # to standard 0-??? port numbers so that the "+" works
1174 # for IP address assignments.
1175 with_ascend_hack = no
1176 ascend_channels_per_line = 23
1178 # Windows NT machines often authenticate themselves as
1179 # NT_DOMAIN\username
1181 # If this is set to 'yes', then the NT_DOMAIN portion
1182 # of the user-name is silently discarded.
1184 # This configuration entry SHOULD NOT be used.
1185 # See the "realms" module for a better way to handle
1187 with_ntdomain_hack = no
1189 # Specialix Jetstream 8500 24 port access server.
1191 # If the user name is 10 characters or longer, a "/"
1192 # and the excess characters after the 10th are
1193 # appended to the user name.
1195 # If you're not running that NAS, you don't need
1197 with_specialix_jetstream_hack = no
1199 # Cisco (and Quintum in Cisco mode) sends it's VSA attributes
1200 # with the attribute name *again* in the string, like:
1202 # H323-Attribute = "h323-attribute=value".
1204 # If this configuration item is set to 'yes', then
1205 # the redundant data in the the attribute text is stripped
1206 # out. The result is:
1208 # H323-Attribute = "value"
1210 # If you're not running a Cisco or Quintum NAS, you don't
1212 with_cisco_vsa_hack = no
1218 # Write a 'utmp' style file, of which users are currently
1219 # logged in, and where they've logged in from.
1221 # This file is used mainly for Simultaneous-Use checking,
1222 # and also 'radwho', to see who's currently logged in.
1225 # Where the file is stored. It's not a log file,
1226 # so it doesn't need rotating.
1228 filename = ${logdir}/radutmp
1230 # The field in the packet to key on for the
1231 # 'user' name, If you have other fields which you want
1232 # to use to key on to control Simultaneous-Use,
1233 # then you can use them here.
1235 # Note, however, that the size of the field in the
1236 # 'utmp' data structure is small, around 32
1237 # characters, so that will limit the possible choices
1240 # You may want instead: %{Stripped-User-Name:-%{User-Name}}
1241 username = %{User-Name}
1244 # Whether or not we want to treat "user" the same
1245 # as "USER", or "User". Some systems have problems
1246 # with case sensitivity, so this should be set to
1247 # 'no' to enable the comparisons of the key attribute
1248 # to be case insensitive.
1250 case_sensitive = yes
1252 # Accounting information may be lost, so the user MAY
1253 # have logged off of the NAS, but we haven't noticed.
1254 # If so, we can verify this information with the NAS,
1256 # If we want to believe the 'utmp' file, then this
1257 # configuration entry can be set to 'no'.
1259 check_with_nas = yes
1261 # Set the file permissions, as the contents of this file
1262 # are usually private.
1271 # Realm module, for proxying.
1273 # You can have multiple instances of the realm module to
1274 # support multiple realm syntaxs at the same time. The
1275 # search order is defined by the order that the modules are listed
1276 # in the authorize and preacct sections.
1278 # Four config options:
1279 # format - must be "prefix" or "suffix"
1280 # The special cases of "DEFAULT"
1281 # and "NULL" are allowed, too.
1282 # delimiter - must be a single character
1286 # Using this entry, IPASS users have their realm set to "IPASS".
1301 realm realmpercent {
1317 # An example configuration for using /etc/smbpasswd.
1319 # See the "passwd" file for documentation on the configuration items
1323 filename = /etc/smbpasswd
1324 format = "*User-Name::LM-Password:NT-Password:SMB-Account-CTRL-TEXT::"
1327 allowmultiplekeys = no
1334 # The rlm_sql_log module appends the SQL queries in a log
1335 # file which is read later by the radsqlrelay program.
1337 # This module only performs the dynamic expansion of the
1338 # variables found in the SQL statements. No operation is
1339 # executed on the database server. (this could be done
1340 # later by an external program) That means the module is
1341 # useful only with non-"SELECT" statements.
1343 # See rlm_sql_log(5) manpage.
1345 # This same functionality could also be implemented by logging
1346 # to a "detail" file, reading that, and then writing to SQL.
1347 # See raddb/sites-available/buffered-sql for an example.
1350 path = "${radacctdir}/sql-relay"
1351 acct_table = "radacct"
1352 postauth_table = "radpostauth"
1353 sql_user_name = "%{%{User-Name}:-DEFAULT}"
1355 Start = "INSERT INTO ${acct_table} (AcctSessionId, UserName, \
1356 NASIPAddress, FramedIPAddress, AcctStartTime, AcctStopTime, \
1357 AcctSessionTime, AcctTerminateCause) VALUES \
1358 ('%{Acct-Session-Id}', '%{User-Name}', '%{NAS-IP-Address}', \
1359 '%{Framed-IP-Address}', '%S', '0', '0', '');"
1360 Stop = "INSERT INTO ${acct_table} (AcctSessionId, UserName, \
1361 NASIPAddress, FramedIPAddress, AcctStartTime, AcctStopTime, \
1362 AcctSessionTime, AcctTerminateCause) VALUES \
1363 ('%{Acct-Session-Id}', '%{User-Name}', '%{NAS-IP-Address}', \
1364 '%{Framed-IP-Address}', '0', '%S', '%{Acct-Session-Time}', \
1365 '%{Acct-Terminate-Cause}');"
1366 Alive = "INSERT INTO ${acct_table} (AcctSessionId, UserName, \
1367 NASIPAddress, FramedIPAddress, AcctStartTime, AcctStopTime, \
1368 AcctSessionTime, AcctTerminateCause) VALUES \
1369 ('%{Acct-Session-Id}', '%{User-Name}', '%{NAS-IP-Address}', \
1370 '%{Framed-IP-Address}', '0', '0', '%{Acct-Session-Time}','');"
1372 Post-Auth = "INSERT INTO ${postauth_table} \
1373 (username, pass, reply, authdate) VALUES \
1374 ('%{User-Name}', '%{User-Password:-Chap-Password}', \
1375 '%{reply:Packet-Type}', '%S');"
1382 # "Safe" radutmp - does not contain caller ID, so it can be
1383 # world-readable, and radwho can work for normal users, without
1384 # exposing any information that isn't already exposed by who(1).
1386 # This is another 'instance' of the radutmp module, but it is given
1387 # then name "sradutmp" to identify it later in the "accounting"
1390 filename = ${logdir}/sradutmp
1398 # Unix /etc/passwd style authentication
1401 # As of 1.1.0, the Unix module no longer reads,
1402 # or caches /etc/passwd, /etc/shadow, or /etc/group.
1403 # If you wish to cache those files, see the passwd
1408 # The location of the "wtmp" file.
1409 # The only use for 'radlast'. If you don't use
1410 # 'radlast', then you can comment out this item.
1412 # Note that the radwtmp file may get large! You should
1413 # rotate it (cp /dev/null radwtmp), or just not use it.
1415 radwtmp = ${logdir}/radwtmp