3 ## clients.conf -- client configuration directives
7 #######################################################################
9 # Define RADIUS clients (usually a NAS, Access Point, etc.).
12 # Defines a RADIUS client.
14 # '127.0.0.1' is another name for 'localhost'. It is enabled by default,
15 # to allow testing of the server after an initial installation. If you
16 # are not going to be permitting RADIUS queries from localhost, we suggest
17 # that you delete, or comment out, this entry.
22 # Each client has a "short name" that is used to distinguish it from
25 # In version 1.x, the string after the word "client" was the IP
26 # address of the client. In 2.0, the IP address is configured via
27 # the "ipaddr" or "ipv6addr" fields. For compatibility, the 1.x
28 # format is still accepted.
32 # dotted quad (1.2.3.4)
33 # hostname (radius.example.com)
36 # OR, you can use an IPv6 address, but not both
38 # ipv6addr = :: # any. ::1 == localhost
41 # A note on DNS: We STRONGLY recommend using IP addresses
42 # rather than host names. Using host names means that the
43 # server will do DNS lookups when it starts, making it
44 # dependent on DNS. i.e. If anything goes wrong with DNS,
45 # the server won't start!
47 # The server also looks up the IP address from DNS once, and
48 # only once, when it starts. If the DNS record is later
49 # updated, the server WILL NOT see that update.
52 # One client definition can be applied to an entire network.
53 # e.g. 127/8 should be defined with "ipaddr = 127.0.0.0" and
56 # If not specified, the default netmask is 32 (i.e. /32)
58 # We do NOT recommend using anything other than 32. There
59 # are usually other, better ways to achieve the same goal.
60 # Using netmasks of other than 32 can cause security issues.
62 # You can specify overlapping networks (127/8 and 127.0/16)
63 # In that case, the smallest possible network will be used
64 # as the "best match" for the client.
66 # Clients can also be defined dynamically at run time, based
67 # on any criteria. e.g. SQL lookups, keying off of NAS-Identifier,
69 # See raddb/sites-available/dynamic-clients for details.
75 # The shared secret use to "encrypt" and "sign" packets between
76 # the NAS and FreeRADIUS. You MUST change this secret from the
77 # default, otherwise it's not a secret any more!
79 # The secret can be any string, up to 8k characters in length.
81 # Control codes can be entered vi octal encoding,
82 # e.g. "\101\102" == "AB"
83 # Quotation marks can be entered by escaping them,
86 # A note on security: The security of the RADIUS protocol
87 # depends COMPLETELY on this secret! We recommend using a
88 # shared secret that is composed of:
94 # And is at LEAST 8 characters long, preferably 16 characters in
95 # length. The secret MUST be random, and should not be words,
96 # phrase, or anything else that is recognizable.
98 # The default secret below is only for testing, and should
99 # not be used in any real environment.
104 # Old-style clients do not send a Message-Authenticator
105 # in an Access-Request. RFC 5080 suggests that all clients
106 # SHOULD include it in an Access-Request. The configuration
107 # item below allows the server to require it. If a client
108 # is required to include a Message-Authenticator and it does
109 # not, then the packet will be silently discarded.
111 # allowed values: yes, no
112 require_message_authenticator = no
115 # The short name is used as an alias for the fully qualified
116 # domain name, or the IP address.
118 # It is accepted for compatibility with 1.x, but it is no
119 # longer necessary in 2.0
121 # shortname = localhost
124 # the following three fields are optional, but may be used by
125 # checkrad.pl for simultaneous use checks
129 # The nastype tells 'checkrad.pl' which NAS-specific method to
130 # use to query the NAS for simultaneous use.
132 # Permitted NAS types are:
146 # other # for all other types
149 nastype = other # localhost isn't usually a NAS...
152 # The following two configurations are for future use.
153 # The 'naspasswd' file is currently used to store the NAS
154 # login name and password, which is used by checkrad.pl
155 # when querying the NAS for simultaneous use.
158 # password = someadminpas
161 # As of 2.0, clients can also be tied to a virtual server.
162 # This is done by setting the "virtual_server" configuration
163 # item, as in the example below.
165 # virtual_server = home1
168 # A pointer to the "home_server_pool" OR a "home_server"
169 # section that contains the CoA configuration for this
170 # client. For an example of a coa home server or pool,
171 # see raddb/sites-available/originate-coa
177 # secret = testing123
178 # shortname = localhost
181 # All IPv6 Site-local clients
183 # secret = testing123
184 # shortname = localhost
187 #client some.host.org {
188 # secret = testing123
189 # shortname = localhost
193 # You can now specify one secret for a network of clients.
194 # When a client request comes in, the BEST match is chosen.
195 # i.e. The entry from the smallest possible network.
197 #client 192.168.0.0/24 {
198 # secret = testing123-1
199 # shortname = private-network-1
202 #client 192.168.0.0/16 {
203 # secret = testing123-2
204 # shortname = private-network-2
208 #client 10.10.10.10 {
209 # # secret and password are mapped through the "secrets" file.
210 # secret = testing123
212 # # the following three fields are optional, but may be used by
213 # # checkrad.pl for simultaneous usage checks
214 # nastype = livingston
216 # password = someadminpas
219 #######################################################################
221 # Per-socket client lists. The configuration entries are exactly
222 # the same as above, but they are nested inside of a section.
224 # You can have as many per-socket client lists as you have "listen"
225 # sections, or you can re-use a list among multiple "listen" sections.
227 # Un-comment this section, and edit a "listen" section to add:
228 # "clients = per_socket_clients". That IP address/port combination
229 # will then accept ONLY the clients listed in this section.
231 #clients per_socket_clients {
232 # client 192.168.3.4 {
233 # secret = testing123