|
|
|
| Enhancements | |
|
|
|
| Release M.10.02 Enhancements | |
|
|
|
|
| |
VENDOR | HP | 11 | ProCurve (HP) |
| |
HP |
|
|
|
| |
ATTRIBUTE | ProCurve (HP) |
| |||
HP |
|
| Attribute for |
| |
|
|
|
| ||
|
|
|
|
|
|
Figure 6. Example of Configuring the VSA for
2.Enter the switch IP address, NAS (Network Attached Server) type, and the key in the FreeRA- DIUS clients.conf file. For example, if the switch IP address is 10.10.10.125 and the key is “1234”, you would enter the following in the server’s clients.conf file:
client 10.10.10.125 nastype = other secret = 1234 
Note: The key configured in the switch and the secret configured in the RADIUS server supporting the switch must be identical. Refer to the chapter titled “RADIUS Authentication and Accounting” in the Access Security Guide for your switch.
Figure 7. Example of Configuring the Switch’s Identity Information in a FreeRADIUS Server
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. Enter the ACEs in an order that promotes optimum traffic management and conservation of system resources, and remember that every ACL you create automatically includes an implicit deny in ip from any to any ACE. (Refer to “Guidelines for Structuring a
•a client having a username of “mobile011” and a password of “run101112”
•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 8 into the FreeRADIUS users file.
Note
For syntax details on
59