blob: a937c8be977109b2f603af66c71cfa602c3eff73 [file] [log] [blame]
Chetan Gaonker7f4bf742016-05-04 15:56:08 -07001#
2# huntgroups This file defines the `huntgroups' that you have. A
3# huntgroup is defined by specifying the IP address of
4# the NAS and possibly a port range. Port can be identified
5# as just one port, or a range (from-to), and multiple ports
6# or ranges of ports must be separated by a comma. For
7# example: 1,2,3-8
8#
9# Matching is done while RADIUS scans the user file; if it
10# includes the selection criterium "Huntgroup-Name == XXX"
11# the huntgroup is looked up in this file to see if it
12# matches. There can be multiple definitions of the same
13# huntgroup; the first one that matches will be used.
14#
15# This file can also be used to define restricted access
16# to certain huntgroups. The second and following lines
17# define the access restrictions (based on username and
18# UNIX usergroup) for the huntgroup.
19#
20
21#
22# Our POP in Alphen a/d Rijn has 3 terminal servers. Create a Huntgroup-Name
23# called Alphen that matches on all three terminal servers.
24#
25#alphen NAS-IP-Address == 192.0.2.5
26#alphen NAS-IP-Address == 192.0.2.6
27#alphen NAS-IP-Address == 192.0.2.7
28
29#
30# The POP in Delft consists of only one terminal server.
31#
32#delft NAS-IP-Address == 198.51.100.5
33
34#
35# Ports 0-7 on the first terminal server in Alphen are connected to
36# a huntgroup that is for business users only. Note that only one
37# of the username or groupname has to match to get access (OR/OR).
38#
39# Note that this huntgroup is a subset of the "alphen" huntgroup.
40#
41#business NAS-IP-Address == 198.51.100.5, NAS-Port-Id == 0-7
42# User-Name = rogerl,
43# User-Name = henks,
44# Group = business,
45# Group = staff
46