Standard Access Control Lists
This chapter describes how to configure a standard ACL and includes the following sections:
Information About Standard ACLs
Standard ACLs identify the destination IP addresses of OSPF routes and can be used in a route map for OSPF redistribution. Standard ACLs cannot be applied to interfaces to control traffic.
Licensing Requirements for Standard ACLs
|
|
---|---|
Guidelines and Limitations
This section includes the guidelines and limitations for this feature:
- Context Mode Guidelines
- Firewall Mode Guidelines
- IPv6 Guidelines
- Additional Guidelines and Limitations
Supported in single context mode only.
Supported in routed and transparent firewall modes.
Additional Guidelines and Limitations
The following guidelines and limitations apply for standard ACLs:
- Standard ACLs identify the destination IP addresses (not source addresses) of OSPF routes and can be used in a route map for OSPF redistribution. Standard ACLs cannot be applied to interfaces to control traffic.
- To add additional ACEs at the end of the ACL, enter another access-list command, specifying the same ACL name.
- When used with the access-group command, the deny keyword does not allow a packet to traverse the ASA. By default, the ASA denies all packets on the originating interface unless you specifically permit access.
- When specifying a source, local, or destination address, use the following guidelines:
– Use a 32-bit quantity in four-part, dotted-decimal format.
– Use the keyword any as an abbreviation for an address and mask of 0.0.0.0.0.0.0.0.
– Use the host ip_address option as an abbreviation for a mask of 255.255.255.255.
Default Settings
Table 23-1 lists the default settings for standard ACL parameters.
Adding Standard ACLs
This section includes the following topics:
Task Flow for Configuring Extended ACLs
Use the following guidelines to create and implement an ACL:
- Create an ACL by adding an ACE and applying an ACL name. See in the Adding Standard ACLs.
- Apply the ACL to an interface. See the firewall configuration guide for more information.
Adding a Standard ACL
To add an ACL to identify the destination IP addresses of OSPF routes, which can be used in a route map for OSPF redistribution, enter the following command:
Adding Remarks to ACLs
You can include remarks about entries in any ACL, including extended, EtherType, IPv6, standard, and Webtype ACLs. The remarks make the ACL easier to understand.
To add a remark after the last access-list command you entered, enter the following command:
Example
You can add a remark before each ACE, and the remarks appear in the ACLs in these location. Entering a dash (-) at the beginning of a remark helps to set it apart from an ACE.
What to Do Next
Apply the ACL to an interface. See the firewall configuration guide for more information.
Monitoring ACLs
To monitor ACLs, perform one of the following tasks:
|
|
---|---|
|
|
|
Configuration Examples for Standard ACLs
The following example shows how to deny IP traffic through the ASA:
ciscoasa(config)# access-list 77 standard deny
The following example shows how to permit IP traffic through the ASA if conditions are matched:
ciscoasa(config)# access-list 77 standard permit
The following example shows how to specify a destination address:
ciscoasa(config)# access-list 77 standard permit host 10.1.10.123
Feature History for Standard ACLs
Table 23-2 lists the release history for this feature.