2 ######################################################################
4 # This is a virtual server that handles *only* inner tunnel
5 # requests for EAP-TTLS and PEAP types.
9 ######################################################################
14 # This next section is here to allow testing of the "inner-tunnel"
15 # authentication methods, independently from the "default" server.
16 # It is listening on "localhost", so that it can only be used from
19 # $ radtest USER PASSWORD 127.0.0.1:18120 0 testing123
21 # If it works, you have configured the inner tunnel correctly. To check
22 # if PEAP will work, use:
24 # $ radtest -t mschap USER PASSWORD 127.0.0.1:18120 0 testing123
26 # If that works, PEAP should work. If that command doesn't work, then
28 # FIX THE INNER TUNNEL CONFIGURATION UNTIL IT WORKS.
30 # Do NOT keep testing PEAP. It won't help.
39 # Authorization. First preprocess (hints and huntgroups files),
40 # then realms, and finally look in the "users" file.
42 # The order of the realm modules will determine the order that
43 # we try to find a matching realm.
45 # Make *sure* that 'preprocess' comes before any realm if you
46 # need to setup hints for the remote radius server
49 # The chap module will set 'Auth-Type := CHAP' if we are
50 # handling a CHAP request and Auth-Type has not already been set
54 # If the users are logging in with an MS-CHAP-Challenge
55 # attribute for authentication, the mschap module will find
56 # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP'
57 # to the request, which will cause the server to then use
58 # the mschap module for authentication.
62 # Pull crypt'd passwords from /etc/passwd or /etc/shadow,
63 # using the system API's to get the password. If you want
64 # to read /etc/passwd or /etc/shadow directly, see the
65 # passwd module, above.
70 # Look for IPASS style 'realm/', and if not found, look for
71 # '@realm', and decide whether or not to proxy, based on
76 # If you are using multiple kinds of realms, you probably
77 # want to set "ignore_null = yes" for all of them.
78 # Otherwise, when the first style of realm doesn't match,
79 # the other styles won't be checked.
81 # Note that proxying the inner tunnel authentication means
82 # that the user MAY use one identity in the outer session
83 # (e.g. "anonymous", and a different one here
84 # (e.g. "user@example.com"). The inner session will then be
85 # proxied elsewhere for authentication. If you are not
86 # careful, this means that the user can cause you to forward
87 # the authentication to another RADIUS server, and have the
88 # accounting logs *not* sent to the other server. This makes
89 # it difficult to bill people for their network activity.
95 # The "suffix" module takes care of stripping the domain
96 # (e.g. "@example.com") from the User-Name attribute, and the
97 # next few lines ensure that the request is not proxied.
99 # If you want the inner tunnel request to be proxied, delete
100 # the next few lines.
103 Proxy-To-Realm := LOCAL
107 # This module takes care of EAP-MSCHAPv2 authentication.
109 # It also sets the EAP-Type attribute in the request
110 # attribute list to the EAP type from the packet.
112 # The example below uses module failover to avoid querying all
113 # of the following modules if the EAP module returns "ok".
114 # Therefore, your LDAP and/or SQL servers will not be queried
115 # for the many packets that go back and forth to set up TTLS
116 # or PEAP. The load on those servers will therefore be reduced.
123 # Read the 'users' file
127 # Look in an SQL database. The schema of the database
128 # is meant to mirror the "users" file.
130 # See "Authorization Queries" in sql.conf
134 # If you are using /etc/smbpasswd, and are also doing
135 # mschap authentication, the un-comment this line, and
136 # configure the 'etc_smbpasswd' module, above.
140 # The ldap module will set Auth-Type to LDAP if it has not
145 # Enforce daily limits on time spent logged in.
149 # Use the checkval module
156 # If no other module has claimed responsibility for
157 # authentication, then try to use PAP. This allows the
158 # other modules listed above to add a "known good" password
159 # to the request, and to do nothing else. The PAP module
160 # will then see that password, and use it to do PAP
163 # This module should be listed last, so that the other modules
164 # get a chance to set Auth-Type for themselves.
173 # This section lists which modules are available for authentication.
174 # Note that it does NOT mean 'try each module in order'. It means
175 # that a module from the 'authorize' section adds a configuration
176 # attribute 'Auth-Type := FOO'. That authentication type is then
177 # used to pick the apropriate module from the list below.
180 # In general, you SHOULD NOT set the Auth-Type attribute. The server
181 # will figure it out on its own, and will do the right thing. The
182 # most common side effect of erroneously setting the Auth-Type
183 # attribute is that one authentication method will work, but the
186 # The common reasons to set the Auth-Type attribute by hand
187 # is to either forcibly reject the user, or forcibly accept him.
191 # PAP authentication, when a back-end database listed
192 # in the 'authorize' section supplies a password. The
193 # password can be clear-text, or encrypted.
199 # Most people want CHAP authentication
200 # A back-end database listed in the 'authorize' section
201 # MUST supply a CLEAR TEXT password. Encrypted passwords
208 # MSCHAP authentication.
214 # Pluggable Authentication Modules.
218 # See 'man getpwent' for information on how the 'unix'
219 # module checks the users password. Note that packets
220 # containing CHAP-Password attributes CANNOT be authenticated
221 # against /etc/passwd! See the FAQ for details.
225 # Uncomment it if you want to use ldap for authentication
227 # Note that this means "check plain-text password against
228 # the ldap database", which means that EAP won't work,
229 # as it does not supply a plain-text password.
235 # Allow EAP authentication.
239 ######################################################################
241 # There are no accounting requests inside of EAP-TTLS or PEAP
244 ######################################################################
247 # Session database, used for checking Simultaneous-Use. Either the radutmp
248 # or rlm_sql module can handle this.
249 # The rlm_sql module is *much* faster
254 # See "Simultaneous Use Checking Queries" in sql.conf
259 # Post-Authentication
260 # Once we KNOW that the user has been authenticated, there are
261 # additional steps we can take.
263 # Note that we do NOT assign IP addresses here.
264 # If you try to assign IP addresses for EAP authentication types,
265 # it WILL NOT WORK. You MUST use DHCP.
268 # If you want to have a log of authentication replies,
269 # un-comment the following line, and the 'detail reply_log'
274 # After authenticating the user, do another SQL query.
276 # See "Authentication Logging Queries" in sql.conf
280 # Instead of sending the query to the SQL server,
281 # write it into a log file.
286 # Un-comment the following if you have set
287 # 'edir_account_policy_check = yes' in the ldap module sub-section of
288 # the 'modules' section.
293 # Access-Reject packets are sent through the REJECT sub-section of the
296 # Add the ldap module name (or instance) if you have set
297 # 'edir_account_policy_check = yes' in the ldap module configuration
299 Post-Auth-Type REJECT {
300 # log failed authentications in SQL, too.
302 attr_filter.access_reject
306 # The example policy below updates the outer tunnel reply
307 # (usually Access-Accept) with the User-Name from the inner
308 # tunnel User-Name. Since this section is processed in the
309 # context of the inner tunnel, "request" here means "inner
310 # tunnel request", and "outer.reply" means "outer tunnel
313 # This example is most useful when the outer session contains
314 # a User-Name of "anonymous@....", or a MAC address. If it
315 # is enabled, the NAS SHOULD use the inner tunnel User-Name
316 # in subsequent accounting packets. This makes it easier to
317 # track user sessions, as they will all be based on the real
318 # name, and not on "anonymous".
320 # The problem with doing this is that it ALSO exposes the
321 # real user name to any intermediate proxies. People use
322 # "anonymous" identifiers outside of the tunnel for a very
323 # good reason: it gives them more privacy. Setting the reply
324 # to contain the real user name removes ALL privacy from
327 # If you want privacy to remain, see the
328 # Chargeable-User-Identity attribute from RFC 4372. In order
329 # to use that attribute, you will have to allocate a
330 # per-session identifier for the user, and store it in a
331 # long-term database (e.g. SQL). You should also use that
332 # attribute INSTEAD of the configuration below.
334 #update outer.reply {
335 # User-Name = "%{request:User-Name}"
341 # When the server decides to proxy a request to a home server,
342 # the proxied request is first passed through the pre-proxy
343 # stage. This stage can re-write the request, or decide to
346 # Only a few modules currently have this method.
351 # Uncomment the following line if you want to change attributes
352 # as defined in the preproxy_users file.
355 # Uncomment the following line if you want to filter requests
356 # sent to remote servers based on the rules defined in the
357 # 'attrs.pre-proxy' file.
358 # attr_filter.pre-proxy
360 # If you want to have a log of packets proxied to a home
361 # server, un-comment the following line, and the
362 # 'detail pre_proxy_log' section, above.
367 # When the server receives a reply to a request it proxied
368 # to a home server, the request may be massaged here, in the
373 # If you want to have a log of replies from a home server,
374 # un-comment the following line, and the 'detail post_proxy_log'
380 # Uncomment the following line if you want to filter replies from
381 # remote proxies based on the rules defined in the 'attrs' file.
382 # attr_filter.post-proxy
385 # If you are proxying LEAP, you MUST configure the EAP
386 # module, and you MUST list it here, in the post-proxy
389 # You MUST also use the 'nostrip' option in the 'realm'
390 # configuration. Otherwise, the User-Name attribute
391 # in the proxied request will not match the user name
392 # hidden inside of the EAP packet, and the end server will
393 # reject the EAP request.
398 # If the server tries to proxy a request and fails, then the
399 # request is processed through the modules in this section.
401 # The main use of this section is to permit robust proxying
402 # of accounting packets. The server can be configured to
403 # proxy accounting packets as part of normal processing.
404 # Then, if the home server goes down, accounting packets can
405 # be logged to a local "detail" file, for processing with
406 # radrelay. When the home server comes back up, radrelay
407 # will read the detail file, and send the packets to the
410 # With this configuration, the server always responds to
411 # Accounting-Requests from the NAS, but only writes
412 # accounting packets to disk if the home server is down.
414 # Post-Proxy-Type Fail {
420 } # inner-tunnel server block