3 ## proxy.conf -- proxy radius and realm configuration directives
7 #######################################################################
9 # Proxy server configuration
11 # This entry controls the servers behaviour towards ALL other servers
12 # to which it sends proxy requests.
16 # Note that as of 2.0, the "synchronous", "retry_delay",
17 # "retry_count", and "dead_time" have all been deprecated.
18 # For backwards compatibility, they are are still accepted
19 # by the server, but they ONLY apply to the old-style realm
20 # configuration. i.e. realms with "authhost" and/or "accthost"
23 # i.e. "retry_delay" and "retry_count" have been replaced
24 # with per-home-server configuration. See the "home_server"
25 # example below for details.
27 # i.e. "dead_time" has been replaced with a per-home-server
28 # "revive_interval". We strongly recommend that this not
29 # be used, however. The new method is much better.
32 # In 2.0, the server is always "synchronous", and setting
33 # "synchronous = no" is impossible. This simplifies the
34 # server and increases the stability of the network.
36 # If you need to set "synchronous = no", please send a
37 # message to the list <freeradius-users@lists.freeradius.org>
38 # explaining why this feature is vital for your network.
41 # If a realm exists, but there are no live home servers for
42 # it, we can fall back to using the "DEFAULT" realm. This is
43 # most useful for accounting, where the server can proxy
44 # accounting requests to home servers, but if they're down,
45 # use a DEFAULT realm that is LOCAL (i.e. accthost = LOCAL),
46 # and then store the packets in the "detail" file. That data
47 # can be later proxied to the home servers by radrelay, when
48 # those home servers come back up again.
50 # Setting this to "yes" may have issues for authentication.
51 # i.e. If you are proxying for two different ISP's, and then
52 # act as a general dial-up for Gric. If one of the first two
53 # ISP's has their RADIUS server go down, you do NOT want to
54 # proxy those requests to GRIC. Instead, you probably want
55 # to just drop the requests on the floor. In that case, set
58 # allowed values: {yes, no}
64 #######################################################################
66 # Configuration for the proxy realms.
68 # As of 2.0. the old-style "realms" file is deprecated, and is not
71 # As of 2.0, the "realm" configuration has changed. Instead of
72 # specifying "authhost" and "accthost" in a realm section, the home
73 # servers are specified seperately in a "home_server" section. For
74 # backwards compatibility, you can still use the "authhost" and
75 # "accthost" directives. If you only have one home server for a
76 # realm, it is easier to use the old-style configuration.
78 # However, if you have multiple servers for a realm, we STRONGLY
79 # suggest moving to the new-style configuration.
82 # Load-balancing and failover between home servers is handled via
83 # a "home_server_pool" section.
85 # Finally, The "realm" section defines the realm, some options, and
86 # indicates which server pool should be used for the realm.
88 # This change means that simple configurations now require multiple
89 # ssections to define a realm. However, complex configurations
90 # are much simpler than before, as multiple realms can share the same
93 # That is, realms point to server pools, and server pools point to
94 # home servers. Multiple realms can point to one server pool. One
95 # server pool can point to multiple home servers. Each home server
96 # can appear in one or more pools.
99 ######################################################################
101 # This section defines a "Home Server" which is another RADIUS
102 # server that gets sent proxied requests. In earlier versions
103 # of FreeRADIUS, home servers were defined in "realm" sections,
104 # which was awkward. In 2.0, they have been made independent
105 # from realms, which is better for a number of reasons.
107 home_server localhost {
109 # Home servers can be sent Access-Request packets
110 # or Accounting-Request packets.
112 # Allowed values are:
113 # auth - Handles Access-Request packets
114 # acct - Handles Accounting-Request packets
115 # auth+acct - Handles Access-Request packets at "port",
116 # and Accounting-Request packets at "port + 1"
117 # coa - Handles CoA-Request and Disconnect-Request packets.
118 # See also raddb/sites-available/originate-coa
122 # Configure ONE OF the following entries:
132 # virtual_server = foo
134 # Note that while both ipaddr and ipv6addr will accept
135 # both addresses and host names, we do NOT recommend
136 # using host names. When you specify a host name, the
137 # server has to do a DNS lookup to find the IP address
138 # of the home server. If the DNS server is slow or
139 # unresponsive, it means that FreeRADIUS will NOT be
140 # able to determine the address, and will therefore NOT
143 # Also, the mapping of host name to address is done ONCE
144 # when the server starts. If DNS is later updated to
145 # change the address, FreeRADIUS will NOT discover that
146 # until after a re-start, or a HUP.
148 # If you specify a virtual_server here, then requests
149 # will be proxied internally to that virtual server.
150 # These requests CANNOT be proxied again, however. The
151 # intent is to have the local server handle packets
152 # when all home servers are dead.
154 # Requests proxied to a virtual server will be passed
155 # through the pre-proxy and post-proxy sections, just
156 # like any other request. See also the sample "realm"
157 # configuration, below.
159 # None of the rest of the home_server configuration is used
160 # for the "virtual_server" configuration.
163 # The port to which packets are sent.
165 # Usually 1812 for type "auth", and 1813 for type "acct".
166 # Older servers may use 1645 and 1646.
167 # Use 3799 for type "coa"
172 # The shared secret use to "encrypt" and "sign" packets between
173 # FreeRADIUS and the home server.
175 # The secret can be any string, up to 8k characters in length.
177 # Control codes can be entered vi octal encoding,
178 # e.g. "\101\102" == "AB"
179 # Quotation marks can be entered by escaping them,
181 # Spaces or other "special" characters can be entered
182 # by putting quotes around the string.
188 ############################################################
190 # The rest of the configuration items listed here are optional,
191 # and do not have to appear in every home server definition.
193 ############################################################
195 # RFC 5080 suggests that all clients SHOULD include it in an
196 # Access-Request. The configuration item below tells the
197 # proxying server (i.e. this one) whether or not the home
198 # server requires a Message-Authenticator attribute. If it
199 # is required (value set to "yes"), then all Access-Request
200 # packets sent to that home server will have a
201 # Message-Authenticator attribute.
203 # allowed values: yes, no
204 require_message_authenticator = no
207 # If the home server doesn't respond to the request within
208 # this time, this server will consider the request dead, and
209 # respond to the NAS with an Access-Reject.
211 # If NO responses are received to any requests sent within this
212 # time period, the home server will be marked "zombie", as below.
214 # Useful range of values: 5 to 60
218 # If the home server does not respond to ANY packets for
219 # a certain time, consider it dead. This time period is
220 # called the "zombie" period, because the server is neither
223 # If "status_check" below is something other than "none", then
224 # the server will start sending status checks at the start of
225 # the zombie period. It will continue sending status checks
226 # until the home server is marked "alive".
228 # Useful range of values: 20 to 120
231 ############################################################
233 # As of 2.0, FreeRADIUS supports RADIUS layer "status
234 # checks". These are used by a proxy server to see if a home
237 # These status packets are sent ONLY if the proxying server
238 # believes that the home server is dead. They are NOT sent
239 # if the proxying server believes that the home server is
240 # alive. They are NOT sent if the proxying server is not
243 # If the home server responds to the status check packet,
244 # then it is marked alive again, and is returned to use.
246 ############################################################
249 # Some home servers do not support status checks via the
250 # Status-Server packet. Others may not have a "test" user
251 # configured that can be used to query the server, to see if
252 # it is alive. For those servers, we have NO WAY of knowing
253 # when it becomes alive again. Therefore, after the server
254 # has been marked dead, we wait a period of time, and mark
255 # it alive again, in the hope that it has come back to
258 # If it has NOT come back to life, then FreeRADIUS will wait
259 # for "zombie_period" before marking it dead again. During
260 # the "zombie_period", ALL AUTHENTICATIONS WILL FAIL, because
261 # the home server is still dead. There is NOTHING that can
262 # be done about this, other than to enable the status checks,
263 # as documented below.
265 # e.g. if "zombie_period" is 40 seconds, and "revive_interval"
266 # is 300 seconds, the for 40 seconds out of every 340, or about
267 # 10% of the time, all authentications will fail.
269 # If the "zombie_period" and "revive_interval" configurations
270 # are set smaller, than it is possible for up to 50% of
271 # authentications to fail.
273 # As a result, we recommend enabling status checks, and
274 # we do NOT recommend using "revive_interval".
276 # The "revive_interval" is used ONLY if the "status_check"
277 # entry below is not "none". Otherwise, it will not be used,
278 # and should be deleted.
280 # Useful range of values: 60 to 3600
281 revive_interval = 120
284 # The proxying server (i.e. this one) can do periodic status
285 # checks to see if a dead home server has come back alive.
287 # If set to "none", then the other configuration items listed
288 # below are not used, and the "revive_interval" time is used
291 # If set to "status-server", the Status-Server packets are
292 # sent. Many RADIUS servers support Status-Server. If a
293 # server does not support it, please contact the server
294 # vendor and request that they add it.
296 # If set to "request", then Access-Request, or Accounting-Request
297 # packets are sent, depending on the "type" entry above (auth/acct).
299 # Allowed values: none, status-server, request
300 status_check = status-server
303 # If the home server does not support Status-Server packets,
304 # then the server can still send Access-Request or
305 # Accounting-Request packets, with a pre-defined user name.
307 # This practice is NOT recommended, as it may potentially let
308 # users gain network access by using these "test" accounts!
310 # If it is used, we recommend that the home server ALWAYS
311 # respond to these Access-Request status checks with
312 # Access-Reject. The status check just needs an answer, it
313 # does not need an Access-Accept.
315 # For Accounting-Request status checks, only the username
316 # needs to be set. The rest of the accounting attribute are
317 # set to default values. The home server that receives these
318 # accounting packets SHOULD NOT treat them like normal user
319 # accounting packets. i.e It should probably NOT log them to
322 # username = "test_user_please_reject_me"
323 # password = "this is really secret"
326 # Configure the interval between sending status check packets.
328 # Setting it too low increases the probability of spurious
329 # fail-over and fallback attempts.
331 # Useful range of values: 6 to 120
335 # Configure the number of status checks in a row that the
336 # home server needs to respond to before it is marked alive.
338 # If you want to mark a home server as alive after a short
339 # time period of being responsive, it is best to use a small
340 # "check_interval", and a large value for
341 # "num_answers_to_alive". Using a long "check_interval" and
342 # a small number for "num_answers_to_alive" increases the
343 # probability of spurious fail-over and fallback attempts.
345 # Useful range of values: 3 to 10
346 num_answers_to_alive = 3
349 # The configuration items in the next sub-section are used ONLY
350 # when "type = coa". It is ignored for all other type of home
353 # See RFC 5080 for the definitions of the following terms.
354 # RAND is a function (internal to FreeRADIUS) returning
355 # random numbers between -0.1 and +0.1
357 # First Re-transmit occurs after:
359 # RT = IRT + RAND*IRT
361 # Subsequent Re-transmits occur after:
363 # RT = 2 * RTprev + RAND * RTprev
365 # Re-trasnmits are capped at:
367 # if (MRT && (RT > MRT)) RT = MRT + RAND * MRT
369 # For a maximum number of attempts: MRC
371 # For a maximum (total) period of time: MRD.
374 # Initial retransmit interval: 1..5
377 # Maximum Retransmit Timeout: 1..30 (0 == no maximum)
380 # Maximum Retransmit Count: 1..20 (0 == retransmit forever)
383 # Maximum Retransmit Duration: 5..60
388 # Sample virtual home server.
389 home_server virtual.example.com {
390 virtual_server = virtual.example.com
393 ######################################################################
395 # This section defines a pool of home servers that is used
396 # for fail-over and load-balancing. In earlier versions of
397 # FreeRADIUS, fail-over and load-balancing were defined per-realm.
398 # As a result, if a server had 5 home servers, each of which served
399 # the same 10 realms, you would need 50 "realm" entries.
401 # In version 2.0, you would need 5 "home_server" sections,
402 # 10 'realm" sections, and one "home_server_pool" section to tie the
405 home_server_pool my_auth_failover {
407 # The type of this pool controls how home servers are chosen.
409 # fail-over - the request is sent to the first live
410 # home server in the list. i.e. If the first home server
411 # is marked "dead", the second one is chosen, etc.
413 # load-balance - the least busy home server is chosen,
414 # where "least busy" is counted by taking the number of
415 # requests sent to that home server, and subtracting the
416 # number of responses received from that home server.
418 # If there are two or more servers with the same low
419 # load, then one of those servers is chosen at random.
420 # This configuration is most similar to the old
421 # "round-robin" method, though it is not exactly the same.
423 # Note that load balancing does not work well with EAP,
424 # as EAP requires packets for an EAP conversation to be
425 # sent to the same home server. The load balancing method
426 # does not keep state in between packets, meaning that
427 # EAP packets for the same conversation may be sent to
428 # different home servers. This will prevent EAP from
431 # For non-EAP authentication methods, and for accounting
432 # packets, we recommend using "load-balance". It will
433 # ensure the highest availability for your network.
435 # client-balance - the home server is chosen by hashing the
436 # source IP address of the packet. If that home server
437 # is down, the next one in the list is used, just as
440 # There is no way of predicting which source IP will map
441 # to which home server.
443 # This configuration is most useful to do simple load
444 # balancing for EAP sessions, as the EAP session will
445 # always be sent to the same home server.
447 # client-port-balance - the home server is chosen by hashing
448 # the source IP address and source port of the packet.
449 # If that home server is down, the next one in the list
450 # is used, just as with "fail-over".
452 # This method provides slightly better load balancing
453 # for EAP sessions than "client-balance". However, it
454 # also means that authentication and accounting packets
455 # for the same session MAY go to different home servers.
457 # keyed-balance - the home server is chosen by hashing (FNV)
458 # the contents of the Load-Balance-Key attribute from the
459 # control items. The request is then sent to home server
462 # server = (hash % num_servers_in_pool).
464 # If there is no Load-Balance-Key in the control items,
465 # the load balancing method is identical to "load-balance".
467 # For most non-EAP authentication methods, The User-Name
468 # attribute provides a good key. An "unlang" policy can
469 # be used to copy the User-Name to the Load-Balance-Key
470 # attribute. This method may not work for EAP sessions,
471 # as the User-Name outside of the TLS tunnel is often
472 # static, e.g. "anonymous@realm".
475 # The default type is fail-over.
479 # A virtual_server may be specified here. If so, the
480 # "pre-proxy" and "post-proxy" sections are called when
481 # the request is proxied, and when a response is received.
483 # This lets you have one policy for all requests that are proxied
484 # to a home server. This policy is completely independent of
485 # any policies used to receive, or process the request.
487 #virtual_server = pre_post_proxy_for_pool
490 # Next, a list of one or more home servers. The names
491 # of the home servers are NOT the hostnames, but the names
492 # of the sections. (e.g. home_server foo {...} has name "foo".
494 # Note that ALL home servers listed here have to be of the same
495 # type. i.e. they all have to be "auth", or they all have to
496 # be "acct", or the all have to be "auth+acct".
498 home_server = localhost
500 # Additional home servers can be listed.
501 # There is NO LIMIT to the number of home servers that can
502 # be listed, though using more than 10 or so will become
503 # difficult to manage.
505 # home_server = foo.example.com
506 # home_server = bar.example.com
507 # home_server = baz.example.com
512 # If ALL home servers are dead, then this "fallback" home server
513 # is used. If set, it takes precedence over any realm-based
514 # fallback, such as the DEFAULT realm.
516 # For reasons of stability, this home server SHOULD be a virtual
517 # server. Otherwise, the fallback may itself be dead!
519 #fallback = virtual.example.com
522 ######################################################################
525 # This section defines a new-style "realm". Note the in version 2.0,
526 # there are many fewer configuration items than in 1.x for a realm.
528 # Automatic proxying is done via the "realms" module (see "man
529 # rlm_realm"). To manually proxy the request put this entry in the
534 #DEFAULT Proxy-To-Realm := "realm_name"
539 # Realms point to pools of home servers.
541 # For authentication, the "auth_pool" configuration item
542 # should point to a "home_server_pool" that was previously
543 # defined. All of the home servers in the "auth_pool" must
546 # For accounting, the "acct_pool" configuration item
547 # should point to a "home_server_pool" that was previously
548 # defined. All of the home servers in the "acct_pool" must
551 # If you have a "home_server_pool" where all of the home servers
552 # are of type "auth+acct", you can just use the "pool"
553 # configuration item, instead of specifying both "auth_pool"
556 auth_pool = my_auth_failover
560 # Normally, when an incoming User-Name is matched against the
561 # realm, the realm name is "stripped" off, and the "stripped"
562 # user name is used to perform matches.
564 # e.g. User-Name = "bob@example.com" will result in two new
565 # attributes being created by the "realms" module:
567 # Stripped-User-Name = "bob"
568 # Realm = "example.com"
570 # The Stripped-User-Name is then used as a key in the "users"
573 # If you do not want this to happen, uncomment "nostrip" below.
577 # There are no more configuration entries for a realm.
582 # This is a sample entry for iPass.
583 # Note that you have to define "ipass_auth_pool" and
584 # "ipass_acct_pool", along with home_servers for them, too.
589 # auth_pool = ipass_auth_pool
590 # acct_pool = ipass_acct_pool
594 # This realm is used mainly to cancel proxying. You can have
595 # the "realm suffix" module configured to proxy all requests for
596 # a realm, and then later cancel the proxying, based on other
599 # For example, you want to terminate PEAP or EAP-TTLS locally,
600 # you can add the following to the "users" file:
602 # DEFAULT EAP-Type == PEAP, Proxy-To-Realm := LOCAL
605 # If we do not specify a server pool, the realm is LOCAL, and
606 # requests are not proxied to it.
610 # This realm is for requests which don't have an explicit realm
611 # prefix or suffix. User names like "bob" will match this one.
614 # authhost = radius.company.com:1600
615 # accthost = radius.company.com:1601
616 # secret = testing123
620 # This realm is for ALL OTHER requests.
623 # authhost = radius.company.com:1600
624 # accthost = radius.company.com:1601
625 # secret = testing123
629 # This realm "proxies" requests internally to a virtual server.
630 # The pre-proxy and post-proxy sections are run just as with any
631 # other kind of home server. The virtual server then receives
632 # the request, and replies, just as with any other packet.
634 # Once proxied internally like this, the request CANNOT be proxied
635 # internally or externally.
637 #realm virtual.example.com {
638 # virtual_server = virtual.example.com
643 # Regular expressions may also be used as realm names. If these are used,
644 # then the "find matching realm" process is as follows:
646 # 1) Look for a non-regex realm with an *exact* match for the name.
647 # If found, it is used in preference to any regex matching realm.
649 # 2) Look for a regex realm, in the order that they are listed
650 # in the configuration files. Any regex match is performed in
651 # a case-insensitive fashion.
653 # 3) If no realm is found, return the DEFAULT realm, if any.
655 # The order of the realms matters in step (2). For example, defining
656 # two realms "*.example.com" and "*.test.example.com" will result in
657 # the second realm NEVER matching. This is because all of the realms
658 # which match the second regex also match the first one. Since the
659 # first regex matches, it is returned.
661 # The solution is to list the realms in the opposite order,. e.g.
662 # "*.test.example.com", followed by "*.example.com".
665 # Some helpful rules:
667 # - always place a '~' character at the start of the realm name.
668 # This signifies that it is a regex match, and not an exact match
671 # - place the regex in double quotes. This helps the configuration
672 # file parser ignore any "special" characters in the regex.
673 # Yes, this rule is different than the normal "unlang" rules for
674 # regular expressions. That may be fixed in a future release.
676 # - use two back-slashes '\\' whenever you need one backslash in the
677 # regex. e.g. "~*\\.example\\.com", and not "~*\.example\.com".
678 # This is because the regex is in a double-quoted string, and normal
679 # rules apply for double-quoted strings.
681 # - If you are matching domain names, use two backslashes in front of
682 # every '.' (dot or period). This is because '.' has special meaning
683 # in a regular expression: match any character. If you do not do this,
684 # then "~*.example.com" will match "fooXexampleYcom", which is likely
687 # - If you are matching domain names, put a '$' at the end of the regex
688 # that matches the domain name. This tells the regex matching code
689 # that the realm ENDS with the domain name, so it does not match
690 # realms with the domain name in the middle. e.g. "~*\\.example\\.com"
691 # will match "test.example.comFOO", which is likely not what you want.
692 # Using "~*\\.example\\.com$" is better.
694 # The more regex realms that are defined, the more time it takes to
695 # process them. You should define as few regex realms as possible
696 # in order to maximize server performance.
698 #realm "~*\\.example\\.com$" {
699 # authhost = LOCAL # not strictly necessary
700 # accthost = LOCAL # not strictly necessary