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
26 # Authorization. First preprocess (hints and huntgroups files),
27 # then realms, and finally look in the "users" file.
29 # The order of the realm modules will determine the order that
30 # we try to find a matching realm.
32 # Make *sure* that 'preprocess' comes before any realm if you
33 # need to setup hints for the remote radius server
36 # The chap module will set 'Auth-Type := CHAP' if we are
37 # handling a CHAP request and Auth-Type has not already been set
41 # If the users are logging in with an MS-CHAP-Challenge
42 # attribute for authentication, the mschap module will find
43 # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP'
44 # to the request, which will cause the server to then use
45 # the mschap module for authentication.
49 # Pull crypt'd passwords from /etc/passwd or /etc/shadow,
50 # using the system API's to get the password. If you want
51 # to read /etc/passwd or /etc/shadow directly, see the
52 # passwd module, above.
57 # Look for IPASS style 'realm/', and if not found, look for
58 # '@realm', and decide whether or not to proxy, based on
63 # If you are using multiple kinds of realms, you probably
64 # want to set "ignore_null = yes" for all of them.
65 # Otherwise, when the first style of realm doesn't match,
66 # the other styles won't be checked.
68 # Note that proxying the inner tunnel authentication means
69 # that the user MAY use one identity in the outer session
70 # (e.g. "anonymous", and a different one here
71 # (e.g. "user@example.com"). The inner session will then be
72 # proxied elsewhere for authentication. If you are not
73 # careful, this means that the user can cause you to forward
74 # the authentication to another RADIUS server, and have the
75 # accounting logs *not* sent to the other server. This makes
76 # it difficult to bill people for their network activity.
82 # The "suffix" module takes care of stripping the domain
83 # (e.g. "@example.com") from the User-Name attribute, and the
84 # next few lines ensure that the request is not proxied.
86 # If you want the inner tunnel request to be proxied, delete
90 Proxy-To-Realm := LOCAL
94 # This module takes care of EAP-MSCHAPv2 authentication.
96 # It also sets the EAP-Type attribute in the request
97 # attribute list to the EAP type from the packet.
99 # The example below uses module failover to avoid querying all
100 # of the following modules if the EAP module returns "ok".
101 # Therefore, your LDAP and/or SQL servers will not be queried
102 # for the many packets that go back and forth to set up TTLS
103 # or PEAP. The load on those servers will therefore be reduced.
110 # Read the 'users' file
114 # Look in an SQL database. The schema of the database
115 # is meant to mirror the "users" file.
117 # See "Authorization Queries" in sql.conf
121 # If you are using /etc/smbpasswd, and are also doing
122 # mschap authentication, the un-comment this line, and
123 # configure the 'etc_smbpasswd' module, above.
127 # The ldap module will set Auth-Type to LDAP if it has not
132 # Enforce daily limits on time spent logged in.
136 # Use the checkval module
143 # If no other module has claimed responsibility for
144 # authentication, then try to use PAP. This allows the
145 # other modules listed above to add a "known good" password
146 # to the request, and to do nothing else. The PAP module
147 # will then see that password, and use it to do PAP
150 # This module should be listed last, so that the other modules
151 # get a chance to set Auth-Type for themselves.
160 # This section lists which modules are available for authentication.
161 # Note that it does NOT mean 'try each module in order'. It means
162 # that a module from the 'authorize' section adds a configuration
163 # attribute 'Auth-Type := FOO'. That authentication type is then
164 # used to pick the apropriate module from the list below.
167 # In general, you SHOULD NOT set the Auth-Type attribute. The server
168 # will figure it out on its own, and will do the right thing. The
169 # most common side effect of erroneously setting the Auth-Type
170 # attribute is that one authentication method will work, but the
173 # The common reasons to set the Auth-Type attribute by hand
174 # is to either forcibly reject the user, or forcibly accept him.
178 # PAP authentication, when a back-end database listed
179 # in the 'authorize' section supplies a password. The
180 # password can be clear-text, or encrypted.
186 # Most people want CHAP authentication
187 # A back-end database listed in the 'authorize' section
188 # MUST supply a CLEAR TEXT password. Encrypted passwords
195 # MSCHAP authentication.
201 # Pluggable Authentication Modules.
205 # See 'man getpwent' for information on how the 'unix'
206 # module checks the users password. Note that packets
207 # containing CHAP-Password attributes CANNOT be authenticated
208 # against /etc/passwd! See the FAQ for details.
212 # Uncomment it if you want to use ldap for authentication
214 # Note that this means "check plain-text password against
215 # the ldap database", which means that EAP won't work,
216 # as it does not supply a plain-text password.
222 # Allow EAP authentication.
226 ######################################################################
228 # There are no accounting requests inside of EAP-TTLS or PEAP
231 ######################################################################
234 # Session database, used for checking Simultaneous-Use. Either the radutmp
235 # or rlm_sql module can handle this.
236 # The rlm_sql module is *much* faster
241 # See "Simultaneous Use Checking Queries" in sql.conf
246 # Post-Authentication
247 # Once we KNOW that the user has been authenticated, there are
248 # additional steps we can take.
250 # Note that we do NOT assign IP addresses here.
251 # If you try to assign IP addresses for EAP authentication types,
252 # it WILL NOT WORK. You MUST use DHCP.
255 # If you want to have a log of authentication replies,
256 # un-comment the following line, and the 'detail reply_log'
261 # After authenticating the user, do another SQL query.
263 # See "Authentication Logging Queries" in sql.conf
267 # Instead of sending the query to the SQL server,
268 # write it into a log file.
273 # Un-comment the following if you have set
274 # 'edir_account_policy_check = yes' in the ldap module sub-section of
275 # the 'modules' section.
280 # Access-Reject packets are sent through the REJECT sub-section of the
283 # Add the ldap module name (or instance) if you have set
284 # 'edir_account_policy_check = yes' in the ldap module configuration
286 Post-Auth-Type REJECT {
287 # log failed authentications in SQL, too.
289 attr_filter.access_reject
293 # The example policy below updates the outer tunnel reply
294 # (usually Access-Accept) with the User-Name from the inner
295 # tunnel User-Name. Since this section is processed in the
296 # context of the inner tunnel, "request" here means "inner
297 # tunnel request", and "outer.reply" means "outer tunnel
300 # This example is most useful when the outer session contains
301 # a User-Name of "anonymous@....", or a MAC address. If it
302 # is enabled, the NAS SHOULD use the inner tunnel User-Name
303 # in subsequent accounting packets. This makes it easier to
304 # track user sessions, as they will all be based on the real
305 # name, and not on "anonymous".
307 # The problem with doing this is that it ALSO exposes the
308 # real user name to any intermediate proxies. People use
309 # "anonymous" identifiers outside of the tunnel for a very
310 # good reason: it gives them more privacy. Setting the reply
311 # to contain the real user name removes ALL privacy from
314 # If you want privacy to remain, see the
315 # Chargeable-User-Identity attribute from RFC 4372. In order
316 # to use that attribute, you will have to allocate a
317 # per-session identifier for the user, and store it in a
318 # long-term database (e.g. SQL). You should also use that
319 # attribute INSTEAD of the configuration below.
321 #update outer.reply {
322 # User-Name = "%{request:User-Name}"
328 # When the server decides to proxy a request to a home server,
329 # the proxied request is first passed through the pre-proxy
330 # stage. This stage can re-write the request, or decide to
333 # Only a few modules currently have this method.
338 # Uncomment the following line if you want to change attributes
339 # as defined in the preproxy_users file.
342 # Uncomment the following line if you want to filter requests
343 # sent to remote servers based on the rules defined in the
344 # 'attrs.pre-proxy' file.
345 # attr_filter.pre-proxy
347 # If you want to have a log of packets proxied to a home
348 # server, un-comment the following line, and the
349 # 'detail pre_proxy_log' section, above.
354 # When the server receives a reply to a request it proxied
355 # to a home server, the request may be massaged here, in the
360 # If you want to have a log of replies from a home server,
361 # un-comment the following line, and the 'detail post_proxy_log'
367 # Uncomment the following line if you want to filter replies from
368 # remote proxies based on the rules defined in the 'attrs' file.
369 # attr_filter.post-proxy
372 # If you are proxying LEAP, you MUST configure the EAP
373 # module, and you MUST list it here, in the post-proxy
376 # You MUST also use the 'nostrip' option in the 'realm'
377 # configuration. Otherwise, the User-Name attribute
378 # in the proxied request will not match the user name
379 # hidden inside of the EAP packet, and the end server will
380 # reject the EAP request.
385 # If the server tries to proxy a request and fails, then the
386 # request is processed through the modules in this section.
388 # The main use of this section is to permit robust proxying
389 # of accounting packets. The server can be configured to
390 # proxy accounting packets as part of normal processing.
391 # Then, if the home server goes down, accounting packets can
392 # be logged to a local "detail" file, for processing with
393 # radrelay. When the home server comes back up, radrelay
394 # will read the detail file, and send the packets to the
397 # With this configuration, the server always responds to
398 # Accounting-Requests from the NAS, but only writes
399 # accounting packets to disk if the home server is down.
401 # Post-Proxy-Type Fail {
407 } # inner-tunnel server block