client 10.10.10.125
Note: The key configured in the switch and the
secret configured in the RADIUS server
supporting the switch must be identical. Refer
nastype = other
secret = 1234
to the chapter titled “RADIUS Authentication
and Accounting” in the latest Access Security
Guide for your switch.
Figure 6-3. Example of Switch Identity Information for a FreeRADIUS Application
3. For a given client username/password pair or MAC address, create an ACL
by entering one or more ACEs in the FreeRADIUS “users” file. Remember
that every ACL you create automatically includes an implicit deny in ip
from any to any ACE. For example, suppose that you wanted to create
identical ACL support for the following:
• a client having a username of “mobilE011” and a password of
“run10kFast”
• a client having a MAC address of 08 E9 9C 4F 00 19
The ACL in this example must achieve the following:
• permit http (TCP port 80) traffic from the client to the device at
10.10.10.101
• deny http (TCP port 80) traffic from the client to all other devices
• permit all other traffic from the client to all other devices
To configure the above ACL, you would enter the username/password and
ACE information shown in figure 6-4 into the FreeRADIUS “users” file.
Example of Configuring a RADIUS-assigned ACL Using the
FreeRADIUS Application
This example illustrates one method for configuring RADIUS-assigned ACL
support for two different client identification methods (username/password
and MAC address). For information on how to configure this functionality on
other RADIUS server types, refer to the documentation provided with the
server.
1. Enter the ProCurve vendor-specific ID and the ACL VSA in the
FreeRADIUS dictionary file:
6-21
To Next Page
Loading...
Need help?
General