-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathservers.example
44 lines (39 loc) · 1.44 KB
/
servers.example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
# The RADIUS servers to query
# Every server must at least contain the "host" key.
#
# It is referred to by its name (the string before the opening curly
# brace). Thus, you can define the same host multiple times with
# different setting if you use distinct names.
#
# The following keys are recognized:
#
# host hostname or ip address to be used [REQUIRED!]
# port port to be used for authentication [default: 1812]
# acctport port to be used for accounting [default: 1813]
# method either one of PAP, CHAP or CUSTOM [default: CHAP]
# bind address or host name to bind to [default: 0.0.0.0]
# secret RADIUS shared secret [default: none]
# priority an integer; bigger means more important [default: 0]
# timeout how long to wait for a response, in ms. [default: 1000]
# The following example defines three RADIUS servers. Two of them have
# the same priority (10), and the order in which they will be queried
# will thus be random. The third (backup) server will *only* be
# queried if the first two have not answered in time (0.5s).
radius1 {
host radius1.example.com
secret v3rYs3cr1t
method CHAP
priority 10
timeout 500
}
radius2 {
host radius2.example.com
secret v3rYs3cr1t
method CHAP
priority 10
timeout 500
}
radius-backup {
host radius3.example.com
secret v3rYs3cr1t
}