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 seperated by a comma. For
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.
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.
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.
25 #alphen NAS-IP-Address == 192.168.2.5
26 #alphen NAS-IP-Address == 192.168.2.6
27 #alphen NAS-IP-Address == 192.168.2.7
30 # The POP in Delft consists of only one terminal server.
32 #delft NAS-IP-Address == 192.168.3.5
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).
39 # Note that this huntgroup is a subset of the "alphen" huntgroup.
41 #business NAS-IP-Address == 192.168.2.5, NAS-Port-Id == 0-7