Applying Access Control to Router Interfaces
Using ACLs Alone to Configure Access Control
5-18
Deleting an Existing ACL
To delete an entire ACL, move to the global configuration mode context and
enter:
Syntax: no ip access-list [extended | standard] <listname>
Replace <listname> with the name of the list you want to delete. For
example, if you wanted to delete an extended ACL list called Inside, you would
enter:
ProCurve (config)# no ip access-list extended Inside
Applying the ACL to an Interface
After you configure an ACL, it will have not control access to an interface until
you apply it to one of the following:
interface
ACP
As discussed above, you can also apply an ACL to all FTP, HTTP, and Telnet
traffic destined to the router.
An ACL can also select traffic for a variety of router functions. You can apply
an ACL to any of the following:
quality of service (QoS) map
crypto map for a Virtual Private Network (VPN)
route map for policy-based routing (PBR)
demand interface to select the traffic that triggers a dial-up connection
rendezvous point (RP) address to select the multicast groups that a PIM-
SM RP supports
This section describes how you apply ACLs to an interface. Table 5-6 lists the
page number where you can find information about how to apply ACLs for
other functions.