1 ######################################################################
3 # As of 2.0.0, FreeRADIUS supports virtual hosts using the
4 # "server" section, and configuration directives.
6 # Virtual hosts should be put into the "sites-available"
7 # directory. Soft links should be created in the "sites-enabled"
8 # directory to these files. This is done in a normal installation.
10 # If you are using 802.1X (EAP) authentication, please see also
11 # the "inner-tunnel" virtual server. You wll likely have to edit
12 # that, too, for authentication to work.
16 ######################################################################
18 # Read "man radiusd" before editing this file. See the section
19 # titled DEBUGGING. It outlines a method where you can quickly
20 # obtain the configuration you want, without running into
21 # trouble. See also "man unlang", which documents the format
24 # This configuration is designed to work in the widest possible
25 # set of circumstances, with the widest possible number of
26 # authentication methods. This means that in general, you should
27 # need to make very few changes to this file.
29 # The best way to configure the server for your local system
30 # is to CAREFULLY edit this file. Most attempts to make large
31 # edits to this file will BREAK THE SERVER. Any edits should
32 # be small, and tested by running the server with "radiusd -X".
33 # Once the edits have been verified to work, save a copy of these
34 # configuration files somewhere. (e.g. as a "tar" file). Then,
35 # make more edits, and test, as above.
37 # There are many "commented out" references to modules such
38 # as ldap, sql, etc. These references serve as place-holders.
39 # If you need the functionality of that module, then configure
40 # it in radiusd.conf, and un-comment the references to it in
41 # this file. In most cases, those small changes will result
42 # in the server being able to connect to the DB, and to
45 ######################################################################
49 # If you want the server to listen on additional addresses, or on
50 # additionnal ports, you can use multiple "listen" sections.
52 # Each section make the server listen for only one type of packet,
53 # therefore authentication and accounting have to be configured in
56 # The server ignore all "listen" section if you are using '-i' and '-p'
57 # on the command line.
60 # Type of packets to listen for.
62 # auth listen for authentication packets
63 # acct listen for accounting packets
64 # proxy IP to use for sending proxied packets
65 # detail Read from the detail file. For examples, see
66 # raddb/sites-available/copy-acct-to-home-server
67 # status listen for Status-Server packets. For examples,
68 # see raddb/sites-available/status
69 # coa listen for CoA-Request and Disconnect-Request
70 # packets. For examples, see the file
71 # raddb/sites-available/coa-server
75 # Note: "type = proxy" lets you control the source IP used for
76 # proxying packets, with some limitations:
78 # * A proxy listener CANNOT be used in a virtual server section.
79 # * You should probably set "port = 0".
80 # * Any "clients" configuration will be ignored.
82 # See also proxy.conf, and the "src_ipaddr" configuration entry
83 # in the sample "home_server" section. When you specify the
84 # source IP address for packets sent to a home server, the
85 # proxy listeners are automatically created.
87 # IP address on which to listen.
89 # dotted quad (1.2.3.4)
90 # hostname (radius.example.com)
94 # OR, you can use an IPv6 address, but not both
96 # ipv6addr = :: # any. ::1 == localhost
98 # Port on which to listen.
100 # integer port number (1812)
101 # 0 means "use /etc/services for the proper port"
104 # Some systems support binding to an interface, in addition
105 # to the IP address. This feature isn't strictly necessary,
106 # but for sites with many IP addresses on one interface,
107 # it's useful to say "listen on all addresses for eth0".
109 # If your system does not support this feature, you will
110 # get an error if you try to use it.
114 # Per-socket lists of clients. This is a very useful feature.
116 # The name here is a reference to a section elsewhere in
117 # radiusd.conf, or clients.conf. Having the name as
118 # a reference allows multiple sockets to use the same
121 # If this configuration is used, then the global list of clients
122 # is IGNORED for this "listen" section. Take care configuring
123 # this feature, to ensure you don't accidentally disable a
126 # See clients.conf for the configuration of "per_socket_clients".
128 # clients = per_socket_clients
131 # Connection limiting for sockets with "proto = tcp".
133 # This section is ignored for other kinds of sockets.
137 # Limit the number of simultaneous TCP connections to the socket
140 # Setting this to 0 means "no limit"
143 # The per-socket "max_requests" option does not exist.
146 # The lifetime, in seconds, of a TCP connection. After
147 # this lifetime, the connection will be closed.
149 # Setting this to 0 means "forever".
153 # The idle timeout, in seconds, of a TCP connection.
154 # If no packets have been received over the connection for
155 # this time, the connection will be closed.
157 # Setting this to 0 means "no timeout".
159 # We STRONGLY RECOMMEND that you set an idle timeout.
166 # This second "listen" section is for listening on the accounting
175 # clients = per_socket_clients
178 # The number of packets received can be rate limited via the
179 # "max_pps" configuration item. When it is set, the server
180 # tracks the total number of packets received in the previous
181 # second. If the count is greater than "max_pps", then the
182 # new packet is silently discarded. This helps the server
183 # deal with overload situations.
185 # The packets/s counter is tracked in a sliding window. This
186 # means that the pps calculation is done for the second
187 # before the current packet was received. NOT for the current
188 # wall-clock second, and NOT for the previous wall-clock second.
190 # Useful values are 0 (no limit), or 100 to 10000.
191 # Values lower than 100 will likely cause the server to ignore
192 # normal traffic. Few systems are capable of handling more than
195 # It is most useful for accounting systems. Set it to 50%
196 # more than the normal accounting load, and you can be sure that
197 # the server will never get overloaded
201 # Only for "proto = tcp". These are ignored for "udp" sockets.
205 # max_connections = 0
209 # Authorization. First preprocess (hints and huntgroups files),
210 # then realms, and finally look in the "users" file.
212 # Any changes made here should also be made to the "inner-tunnel"
215 # The order of the realm modules will determine the order that
216 # we try to find a matching realm.
218 # Make *sure* that 'preprocess' comes before any realm if you
219 # need to setup hints for the remote radius server
222 # Take a User-Name, and perform some checks on it, for spaces and other
223 # invalid characters. If the User-Name appears invalid, reject the
226 # See policy.d/filter for the definition of the filter_username policy.
231 # The preprocess module takes care of sanitizing some bizarre
232 # attributes in the request, and turning them into attributes
233 # which are more standard.
235 # It takes care of processing the 'raddb/hints' and the
236 # 'raddb/huntgroups' files.
239 # If you intend to use CUI and you require that the Operator-Name
240 # be set for CUI generation and you want to generate CUI also
241 # for your local clients then uncomment the operator-name
242 # below and set the operator-name for your clients in clients.conf
246 # If you want to generate CUI for some clients that do not
247 # send proper CUI requiests, then uncomment the
248 # cui below and set "add-cui = yes" for these clients in clients.conf
252 # If you want to have a log of authentication requests,
253 # un-comment the following line, and the 'detail auth_log'
258 # The chap module will set 'Auth-Type := CHAP' if we are
259 # handling a CHAP request and Auth-Type has not already been set
263 # If the users are logging in with an MS-CHAP-Challenge
264 # attribute for authentication, the mschap module will find
265 # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP'
266 # to the request, which will cause the server to then use
267 # the mschap module for authentication.
271 # If you have a Cisco SIP server authenticating against
272 # FreeRADIUS, uncomment the following line, and the 'digest'
273 # line in the 'authenticate' section.
277 # The WiMAX specification says that the Calling-Station-Id
278 # is 6 octets of the MAC. This definition conflicts with
279 # RFC 3580, and all common RADIUS practices. Un-commenting
280 # the "wimax" module here means that it will fix the
281 # Calling-Station-Id attribute to the normal format as
282 # specified in RFC 3580 Section 3.21
286 # Look for IPASS style 'realm/', and if not found, look for
287 # '@realm', and decide whether or not to proxy, based on
292 # If you are using multiple kinds of realms, you probably
293 # want to set "ignore_null = yes" for all of them.
294 # Otherwise, when the first style of realm doesn't match,
295 # the other styles won't be checked.
301 # This module takes care of EAP-MD5, EAP-TLS, and EAP-LEAP
304 # It also sets the EAP-Type attribute in the request
305 # attribute list to the EAP type from the packet.
307 # As of 2.0, the EAP module returns "ok" in the authorize stage
308 # for TTLS and PEAP. In 1.x, it never returned "ok" here, so
309 # this change is compatible with older configurations.
311 # The example below uses module failover to avoid querying all
312 # of the following modules if the EAP module returns "ok".
313 # Therefore, your LDAP and/or SQL servers will not be queried
314 # for the many packets that go back and forth to set up TTLS
315 # or PEAP. The load on those servers will therefore be reduced.
322 # Pull crypt'd passwords from /etc/passwd or /etc/shadow,
323 # using the system API's to get the password. If you want
324 # to read /etc/passwd or /etc/shadow directly, see the
325 # passwd module in radiusd.conf.
330 # Read the 'users' file
334 # Look in an SQL database. The schema of the database
335 # is meant to mirror the "users" file.
337 # See "Authorization Queries" in sql.conf
341 # If you are using /etc/smbpasswd, and are also doing
342 # mschap authentication, the un-comment this line, and
343 # configure the 'smbpasswd' module.
347 # The ldap module reads passwords from the LDAP database.
351 # Enforce daily limits on time spent logged in.
359 # If no other module has claimed responsibility for
360 # authentication, then try to use PAP. This allows the
361 # other modules listed above to add a "known good" password
362 # to the request, and to do nothing else. The PAP module
363 # will then see that password, and use it to do PAP
366 # This module should be listed last, so that the other modules
367 # get a chance to set Auth-Type for themselves.
372 # If "status_server = yes", then Status-Server messages are passed
373 # through the following section, and ONLY the following section.
374 # This permits you to do DB queries, for example. If the modules
375 # listed here return "fail", then NO response is sent.
377 # Autz-Type Status-Server {
386 # This section lists which modules are available for authentication.
387 # Note that it does NOT mean 'try each module in order'. It means
388 # that a module from the 'authorize' section adds a configuration
389 # attribute 'Auth-Type := FOO'. That authentication type is then
390 # used to pick the apropriate module from the list below.
393 # In general, you SHOULD NOT set the Auth-Type attribute. The server
394 # will figure it out on its own, and will do the right thing. The
395 # most common side effect of erroneously setting the Auth-Type
396 # attribute is that one authentication method will work, but the
399 # The common reasons to set the Auth-Type attribute by hand
400 # is to either forcibly reject the user (Auth-Type := Reject),
401 # or to or forcibly accept the user (Auth-Type := Accept).
403 # Note that Auth-Type := Accept will NOT work with EAP.
405 # Please do not put "unlang" configurations into the "authenticate"
406 # section. Put them in the "post-auth" section instead. That's what
407 # the post-auth section is for.
411 # PAP authentication, when a back-end database listed
412 # in the 'authorize' section supplies a password. The
413 # password can be clear-text, or encrypted.
419 # Most people want CHAP authentication
420 # A back-end database listed in the 'authorize' section
421 # MUST supply a CLEAR TEXT password. Encrypted passwords
428 # MSCHAP authentication.
434 # If you have a Cisco SIP server authenticating against
435 # FreeRADIUS, uncomment the following line, and the 'digest'
436 # line in the 'authorize' section.
440 # Pluggable Authentication Modules.
443 # Uncomment it if you want to use ldap for authentication
445 # Note that this means "check plain-text password against
446 # the ldap database", which means that EAP won't work,
447 # as it does not supply a plain-text password.
449 # We do NOT recommend using this. LDAP servers are databases.
450 # They are NOT authentication servers. FreeRADIUS is an
451 # authentication server, and knows what to do with authentication.
452 # LDAP servers do not.
459 # Allow EAP authentication.
463 # The older configurations sent a number of attributes in
464 # Access-Challenge packets, which wasn't strictly correct.
465 # If you want to filter out these attributes, uncomment
466 # the following lines.
472 # if (handled && (Response-Packet-Type == Access-Challenge)) {
473 # attr_filter.access_challenge.post-auth
474 # handled # override the "updated" code from attr_filter
481 # Pre-accounting. Decide which accounting type to use.
487 # Session start times are *implied* in RADIUS.
488 # The NAS never sends a "start time". Instead, it sends
489 # a start packet, *possibly* with an Acct-Delay-Time.
490 # The server is supposed to conclude that the start time
491 # was "Acct-Delay-Time" seconds in the past.
493 # The code below creates an explicit start time, which can
494 # then be used in other modules. It will be *mostly* correct.
495 # Any errors are due to the 1-second resolution of RADIUS,
496 # and the possibility that the time on the NAS may be off.
498 # The start time is: NOW - delay - session_length
502 # FreeRADIUS-Acct-Session-Start-Time = "%{expr: %l - %{%{Acct-Session-Time}:-0} - %{%{Acct-Delay-Time}:-0}}"
507 # Ensure that we have a semi-unique identifier for every
508 # request, and many NAS boxes are broken.
512 # Look for IPASS-style 'realm/', and if not found, look for
513 # '@realm', and decide whether or not to proxy, based on
516 # Accounting requests are generally proxied to the same
517 # home server as authentication requests.
523 # Read the 'acct_users' file
528 # Accounting. Log the accounting data.
531 # Update accounting packet by adding the CUI attribute
532 # recorded from the corresponding Access-Accept
533 # use it only if your NAS boxes do not support CUI themselves
536 # Create a 'detail'ed log of the packets.
537 # Note that accounting requests which are proxied
538 # are also logged in the detail file.
542 # Update the wtmp file
544 # If you don't use "radlast", you can delete this line.
548 # For Simultaneous-Use tracking.
550 # Due to packet losses in the network, the data here
551 # may be incorrect. There is little we can do about it.
555 # Return an address to the IP Pool when we see a stop record.
559 # Log traffic to an SQL database.
561 # See "Accounting queries" in sql.conf
565 # If you receive stop packets with zero session length,
566 # they will NOT be logged in the database. The SQL module
567 # will print a message (only in debugging mode), and will
570 # You can ignore these packets by uncommenting the following
571 # three lines. Otherwise, the server will not respond to the
572 # accounting request, and the NAS will retransmit.
579 # Instead of sending the query to the SQL server,
580 # write it into a log file.
584 # Cisco VoIP specific bulk accounting
587 # For Exec-Program and Exec-Program-Wait
590 # Filter attributes from the accounting response.
591 attr_filter.accounting_response
594 # See "Autz-Type Status-Server" for how this works.
596 # Acct-Type Status-Server {
602 # Session database, used for checking Simultaneous-Use. Either the radutmp
603 # or rlm_sql module can handle this.
604 # The rlm_sql module is *much* faster
609 # See "Simultaneous Use Checking Queries" in sql.conf
614 # Post-Authentication
615 # Once we KNOW that the user has been authenticated, there are
616 # additional steps we can take.
618 # Get an address from the IP Pool.
622 # If you want to have a log of authentication replies,
623 # un-comment the following line, and enable the
624 # 'detail reply_log' module.
628 # After authenticating the user, do another SQL query.
630 # See "Authentication Logging Queries" in sql.conf
634 # Instead of sending the query to the SQL server,
635 # write it into a log file.
640 # Un-comment the following if you want to modify the user's object
641 # in LDAP after a successful login.
645 # For Exec-Program and Exec-Program-Wait
649 # Calculate the various WiMAX keys. In order for this to work,
650 # you will need to define the WiMAX NAI, usually via
653 # WiMAX-MN-NAI = "%{User-Name}"
656 # If you want various keys to be calculated, you will need to
657 # update the reply with "template" values. The module will see
658 # this, and replace the template values with the correct ones
659 # taken from the cryptographic calculations. e.g.
662 # WiMAX-FA-RK-Key = 0x00
663 # WiMAX-MSK = "%{EAP-MSK}"
666 # You may want to delete the MS-MPPE-*-Keys from the reply,
667 # as some WiMAX clients behave badly when those attributes
668 # are included. See "raddb/modules/wimax", configuration
669 # entry "delete_mppe_keys" for more information.
673 # Create the CUI value and add the attribute to Access-Accept.
674 # Uncomment the line below if *returning* the CUI.
677 # If there is a client certificate (EAP-TLS, sometimes PEAP
678 # and TTLS), then some attributes are filled out after the
679 # certificate verification has been performed. These fields
680 # MAY be available during the authentication, or they may be
681 # available only in the "post-auth" section.
683 # The first set of attributes contains information about the
684 # issuing certificate which is being used. The second
685 # contains information about the client certificate (if
689 # Reply-Message += "%{TLS-Cert-Serial}"
690 # Reply-Message += "%{TLS-Cert-Expiration}"
691 # Reply-Message += "%{TLS-Cert-Subject}"
692 # Reply-Message += "%{TLS-Cert-Issuer}"
693 # Reply-Message += "%{TLS-Cert-Common-Name}"
694 # Reply-Message += "%{TLS-Cert-Subject-Alt-Name-Email}"
696 # Reply-Message += "%{TLS-Client-Cert-Serial}"
697 # Reply-Message += "%{TLS-Client-Cert-Expiration}"
698 # Reply-Message += "%{TLS-Client-Cert-Subject}"
699 # Reply-Message += "%{TLS-Client-Cert-Issuer}"
700 # Reply-Message += "%{TLS-Client-Cert-Common-Name}"
701 # Reply-Message += "%{TLS-Client-Cert-Subject-Alt-Name-Email}"
704 # Insert class attribute (with unique value) into response,
705 # aids matching auth and acct records, and protects against duplicate
706 # Acct-Session-Id. Note: Only works if the NAS has implemented
707 # RFC 2865 behaviour for the class attribute, AND if the NAS
708 # supports long Class attributes. Many older or cheap NASes
709 # only support 16-octet Class attributes.
712 # MacSEC requires the use of EAP-Key-Name. However, we don't
713 # want to send it for all EAP sessions. Therefore, the EAP
714 # modules put required data into the EAP-Session-Id attribute.
715 # This attribute is never put into a request or reply packet.
717 # Uncomment the next few lines to copy the required data into
718 # the EAP-Key-Name attribute
719 # if (reply:EAP-Session-Id) {
721 # EAP-Key-Name := "%{reply:EAP-Session-Id}"
725 # Remove reply message if the response contains an EAP-Message
726 remove_reply_message_if_eap
729 # Access-Reject packets are sent through the REJECT sub-section of the
732 # Add the ldap module name (or instance) if you have set
733 # 'edir_account_policy_check = yes' in the ldap module configuration
735 Post-Auth-Type REJECT {
736 # log failed authentications in SQL, too.
738 attr_filter.access_reject
740 # Insert EAP-Failure message if the request was
741 # rejected by policy instead of because of an
742 # authentication failure
745 # Remove reply message if the response contains an EAP-Message
746 remove_reply_message_if_eap
751 # When the server decides to proxy a request to a home server,
752 # the proxied request is first passed through the pre-proxy
753 # stage. This stage can re-write the request, or decide to
756 # Only a few modules currently have this method.
759 # Before proxing the request add an Operator-Name attribute identifying
760 # if the operator-name is found for this client.
761 # No need to uncomment this if you have already enabled this in
762 # the authorize section.
765 # The client requests the CUI by sending a CUI attribute
766 # containing one zero byte.
767 # Uncomment the line below if *requesting* the CUI.
770 # Uncomment the following line if you want to change attributes
771 # as defined in the preproxy_users file.
774 # Uncomment the following line if you want to filter requests
775 # sent to remote servers based on the rules defined in the
776 # 'attrs.pre-proxy' file.
777 # attr_filter.pre-proxy
779 # If you want to have a log of packets proxied to a home
780 # server, un-comment the following line, and the
781 # 'detail pre_proxy_log' section, above.
786 # When the server receives a reply to a request it proxied
787 # to a home server, the request may be massaged here, in the
792 # If you want to have a log of replies from a home server,
793 # un-comment the following line, and the 'detail post_proxy_log'
797 # Uncomment the following line if you want to filter replies from
798 # remote proxies based on the rules defined in the 'attrs' file.
799 # attr_filter.post-proxy
802 # If you are proxying LEAP, you MUST configure the EAP
803 # module, and you MUST list it here, in the post-proxy
806 # You MUST also use the 'nostrip' option in the 'realm'
807 # configuration. Otherwise, the User-Name attribute
808 # in the proxied request will not match the user name
809 # hidden inside of the EAP packet, and the end server will
810 # reject the EAP request.
815 # If the server tries to proxy a request and fails, then the
816 # request is processed through the modules in this section.
818 # The main use of this section is to permit robust proxying
819 # of accounting packets. The server can be configured to
820 # proxy accounting packets as part of normal processing.
821 # Then, if the home server goes down, accounting packets can
822 # be logged to a local "detail" file, for processing with
823 # radrelay. When the home server comes back up, radrelay
824 # will read the detail file, and send the packets to the
827 # With this configuration, the server always responds to
828 # Accounting-Requests from the NAS, but only writes
829 # accounting packets to disk if the home server is down.
831 # Post-Proxy-Type Fail {