Creating An Extended Acl - HP ProCurve Secure Router 7203 dl Advanced Management And Configuration Manual

Selecting the log Option. Include the log option if you want the Secure
Router OS to log a message when these two conditions are met:
debug access-list is enabled for this ACL
a packet matches this ACL
Exit the ACL. After you have finished creating the ACL, enter exit to return
to the global configuration mode context, as shown below:
ProCurve(config-std-nacl)# exit
ProCurve(config)#

Creating an Extended ACL

To create an extended ACL, you enter the following command from the global
configuration mode context:
ProCurve(config)# ip access-list extended <listname>
Replace <listname> with an alphanumeric descriptor that is meaningful to
you. The name is case sensitive.
After you enter this command, you are moved to the extended ACL configu-
ration mode context:
ProCurve(config-ext-nacl)#
Using Permit and Deny Entries to Select Traffic. You can now begin to
enter permit and deny entries. Because you are applying the ACL to an ACP,
you will use a permit entry to select the traffic for the action you specify in
the ACP. You will use a deny entry to exclude the traffic from the action you
specify in the ACP. The ACL is empty until you add these entries.
To create permit and deny entries for extended ACLs, use the following
command syntax:
Syntax: [permit | deny] <protocol> <source address> <source port> <destination
address> <destination port> [<packet bits>] [log | log-input]
You must specify a <protocol>, <source address>, and <destination
address>. However, the following are optional:
<source port> for TCP or UDP traffic
<destination port> for TCP or UDP traffic
<packet bits>
[log | log-input]
Applying Access Control to Router Interfaces
Using ACPs to Control Access to Router Interfaces
5-31