CLI Book 1: Cisco ASA Series General Operations CLI Configuration Guide, 9.1
Adding a Standard Access List
Downloads: This chapterpdf (PDF - 208.0KB) The complete bookPDF (PDF - 12.94MB) | The complete bookePub (ePub - 2.91MB) | The complete bookMobi (Mobi - 4.44MB) | Feedback

Table of Contents

Adding a Standard Access Control List

Information About Standard ACLs

Licensing Requirements for Standard ACLs

Guidelines and Limitations

Default Settings

Adding Standard ACLs

Task Flow for Configuring Extended ACLs

Adding a Standard ACL

Adding Remarks to ACLs

What to Do Next

Monitoring ACLs

Configuration Examples for Standard ACLs

Feature History for Standard ACLs

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

The following table shows the licensing requirements for this feature:

 

Model
License Requirement

All models

Base License.

Guidelines and Limitations

This section includes the guidelines and limitations for this feature:

Context Mode Guidelines

Supported in single context mode only.

Firewall Mode Guidelines

Supported in routed and transparent firewall modes.

IPv6 Guidelines

Supports IPv6.

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.

  • You can disable an ACE by specifying the keyword inactive in the access-list command.

Default Settings

Table 21-1 lists the default settings for standard ACL parameters.

 

Table 21-1 Default Standard ACL Parameters

Parameters
Default

deny

The ASA denies all packets on the originating interface unless you specifically permit access.

ACL logging generates system log message 106023 for denied packets. Deny packets must be present to log denied packets.

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:

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:

 

Command
Purpose
hostname(config)# access-list access_list_name standard { deny | permit } { any4 | ip_address mask }
 

ciscoasa(config)# access-list OSPF standard permit 192.168.1.0 255.255.255.0

 

Adds a standard access list entry. To add another ACE to the end of the ACL, enter another access-list command, specifying the same ACL name.

The access_list_name argument specifies the name of number of an ACL.

The any4 keyword specifies access to anyone.

The deny keyword denies access if the conditions are matched.

The host ip_address syntax specifies access to a host IP address.

The ip_address ip_mask argument specifies access to a specific IP address and subnet mask.

The line line-num option specifies the line number at which to insert an ACE.

The permit keyword permits access if the conditions are matched.

To remove an ACE, enter the no access-list command with the entire command syntax string as it appears in the configuration.

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:

 

Command
Purpose
access-list access_list_name remark text
 
ciscoasa(config)# access-list OUT remark - this is the inside admin address
 

 

Adds a remark after the last access-list command you entered.

The text can be up to 100 characters in length. You can enter leading spaces at the beginning of the text. Trailing spaces are ignored.

If you enter the remark before any access-list command, then the remark is the first line in the ACL.

If you delete an ACL using the no access-list access_list_name command, then all the remarks are also removed.

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.

ciscoasa(config)# access-list OUT remark - this is the inside admin address
ciscoasa(config)# access-list OUT extended permit ip host 209.168.200.3 any
ciscoasa(config)# access-list OUT remark - this is the hr admin address
ciscoasa(config)# access-list OUT extended permit ip host 209.168.200.4 any
 

What to Do Next

Apply the ACL to an interface. See the “Configuring Access Rules” section in the firewall configuration guide for more information.

Monitoring ACLs

To monitor ACLs, perform one of the following tasks:

 

Command
Purpose
show access-list

Displays the ACL entries by number.

show running-config access-list

Displays the current running access-list configuration.

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 21-2 lists the release history for this feature.

 

Table 21-2 Feature History for Standard ACLs

Feature Name
Releases
Feature Information

Standard ACLs

7.0(1)

Standard ACLs identify the destination IP addresses of OSPF routes, which can be used in a route map for OSPF redistribution.

We introduced the feature and the following command: access-list standard .