IPv4 Access Control Lists (ACLs)
Editing an Existing ACL
For example, to append a fourth ACE to the end of the ACL in figure 9-16:
P
roCurve(config)# ip access-list standard My-List
ProCurve(config-std-nacl)# permit any
ProCurve(config-std-nacl)# show run
.
.
.
ip access-list standard "My-List"
10 permit 10.10.10.25 0.0.0.0
20 permit 10.20.10.117 0.0.0.0
30 deny 10.20.10.1 0.0.0.255
40 permit 0.0.0.0 255.255.255.255
exit
Figure 9-18. Example of Appending an ACE to an Existing List
Note When using the access-list < 1 - 99 | 100 - 199 > < permit | deny > < SA > command
to create an ACE for a numbered ACL, the ACE is always added to the end of
the current list and given the appropriate sequence number. However, once a
numbered list has been created, you can use the ip access-list command to
open it as a named ACL and specify a nondefault sequence number, as
described in the next section.
Inserting an ACE in an Existing ACL
This action uses a sequence number to specify where to insert a new ACE into
an existing sequence of ACLs.
Syntax: ip access-list < standard | extended > < name-str | 1 - 99 | 100 - 199 >
<1-2147483647> < permit | deny > < standard-acl-ip-criteria > [ log ]
<1-2147483647> < permit | deny > < extended-acl-ip-criteria > [ options ]
The first command enters the “Named-ACL” context for the
specified ACL. The remaining two commands insert a new
ACE in a standard or extended ACL, respectively. (For details
on these criteria and options, refer to table 9-1, “Command
Summary for Standard IPv4 ACLs” —page 9-6, and table 9-2,
“Command Summary for IPv4 Extended ACLs” —page 9-8.)
To insert a new ACE between existing ACEs in a list:
1. Use ip access-list to enter the “Named-ACL” (nacl) context of the ACE.
This applies regardless of whether the ACE was originally created as a
numbered ACL or a named ACL.
9-77
To Next Page
Loading...
Need help?
General