- Preface
- Using the WAAS Command-Line Interface
- Cisco WAAS Software Command Summary
- CLI Commands
- EXEC Mode Commands
- Global Configuration Mode Commands
- Interface Configuration Mode Commands
- Standard ACL Configuration Mode Commands
- Extended ACL Configuration Mode Commands
- PKI Certificate Authority Configuration Mode Commands
- PKI Global Settings Configuration Mode Commands
- SSL Accelerated Service Configuration Mode Commands
- SSL Cipher List Configuration Mode Commands
- SSL Global Service Configuration Mode Commands
- SSL Host Peering Service Configuration Mode Commands
- SSL Management Service Configuration Mode Commands
- WCCP Configuration Mode Commands
- Class Map Configuration Mode Commands
- Policy Map Configuration Mode Commands
- Policy Map Class Configuration Mode Commands
- Acronyms and Abbreviations
- Command Summary by Mode
Extended ACL Configuration Mode Commands
To create and modify extended access lists on a WAAS device for controlling access to interfaces or applications, use the ip access-list extended global configuration command. To disable an extended access list, use the no form of this command.
ip access-list extended { acl-name | acl-num }
no ip access-list extended { acl-name | acl-num }
Syntax Description
Defaults
An access list drops all packets unless you configure at least one permit entry.
Command Modes
Device Modes
Usage Guidelines
Within ACL configuration mode, you can use the editing commands (list, delete, and move) to display the current condition entries, to delete a specific entry, or to change the order in which the entries will be evaluated. To return to global configuration mode, enter the exit command at the ACL configuration mode prompt.
To create an entry, use a deny or permit keyword and specify the type of packets that you want the WAAS device to drop or to accept for further processing. By default, an access list denies everything because the list is terminated by an implicit deny any entry. Therefore, you must include at least one permit entry to create a valid access list.
Note ACLs that are defined on a router take precedence over the ACLs that are defined on the WAE. ACLs that are defined on a WAE take precedence over the WAAS application definition policies that are defined on the WAE.
After creating an access list, you can include the access list in an access group using the access-group command, which determines how the access list is applied. You can also apply the access list to a specific application using the appropriate command. A reference to an access list that does not exist is the equivalent of a permit any condition statement.
To create an extended access list, enter the ip access-list extended global configuration command. Identify the new or existing access list with a name up to 30 characters long beginning with a letter, or with a number. If you use a number to identify an extended access list, it must be from 100 to 199
Note You must use a standard access list for providing access to the SNMP server or to the TFTP gateway/server. However, you can use either a standard access list or an extended access list for providing access to the WCCP application.
To allow connections from a specific host, use the permit host source-ip option and replace source-ip with the IP address of the specific host.
To allow connections from a specific network, use the permit host source-ip wildcard option. Replace source-ip with a network ID or the IP address of any host on the network that you want to specify. Replace wildcard with the dotted decimal notation for a mask that is the reverse of a subnet mask, where a 0 indicates a position that must be matched and a 1 indicates a position that does not matter. For instance, the wildcard 0.0.0.255 causes the last eight bits in the source IP address to be ignored. Therefore, the permit 192.168.1.0 0.0.0.255 entry allows access from any host on the 192.168.1.0 network.
After you identify the extended access list, the CLI enters the extended ACL configuration mode and all subsequent commands apply to the specified access list.
Examples
The following example shows how to create an access list on the WAAS device. You create this access list to allow the WAAS device to accept all web traffic that is redirected to it but limit host administrative access using SSH:
The following example shows how to activate the access list for an interface:
The following example shows how this configuration appears when you enter the show running-configuration command:
Related Commands
(config-ext-nacl) delete
To delete a line from the extended ACL, use the delete extended ACL configuration command.
Syntax Description
Defaults
Command Modes
extended ACL configuration mode
Device Modes
Examples
The following example shows how to delete line 10 from the extended ACL testextacl:
Related Commands
(config-ext-nacl) deny
To add a line to an extended access list that specifies the type of packets that you want the WAAS device to drop, use the deny extended ACL configuration command. To add a condition to the extended ACL, note that the options depend on the chosen protocol.
For IP, use the following syntax to add a condition:
[ insert line-num ] deny { gre | icmp | tcp | udp | ip | proto-num } { source-ip [ wildcard ] |
host source-ip | any } { dest-ip [ wildcard ] | host dest-ip | any }
no deny { gre | icmp | tcp | udp | ip | proto-num } { source-ip [ wildcard ] | host source-ip | any } { dest-ip [ wildcard ] | host dest-ip | any }
For TCP, use the following syntax to add a condition:
[ insert line-num ] deny tcp { source-ip [ wildcard ] | host source-ip | any } [ operator port [ port ]] { dest-ip [ wildcard ] | host dest-ip | any } [ operator port [ port ]] [ established ]
no deny tcp { source-ip [ wildcard ] | host source-ip | any } [ operator port [ port ]]
{ dest-ip [ wildcard ] | host dest-ip | any } [ operator port [ port ]] [ established ]
For UDP, use the following syntax to add a condition:
[ insert line-num ] deny udp { source-ip [ wildcard ] | host source-ip | any } [ operator port [ port ]] { dest-ip [ wildcard ] | host dest-ip | any } [ operator port [ port ]]
no deny udp { source-ip [ wildcard ] | host source-ip | any } [ operator port [ port ]]
{ dest-ip [ wildcard ] | host dest-ip | any } [ operator port [ port ]]
For ICMP, use the following syntax to add a condition:
[ insert line-num ] deny icmp { source-ip [ wildcard ] | host source-ip | any } { dest-ip [ wildcard ] |
host dest-ip | any } [ icmp-type [ code ] | icmp-msg ]
no deny icmp { source-ip [ wildcard ] | host source-ip | any } { dest-ip [ wildcard ] | host dest-ip | any } [ icmp-type [ code ] | icmp-msg ]
Syntax Description
Defaults
An access list drops all packets unless you configure at least one permit entry.
Command Modes
extended ACL configuration mode
Device Modes
Usage Guidelines
To create an entry, use a deny or permit keyword and specify the type of packets that you want the WAAS device to drop or to accept for further processing. By default, an access list denies everything because the list is terminated by an implicit deny any entry. You must include at least one permit entry to create a valid access list.
To allow connections from a specific host, use the permit host source-ip option and replace source-ip with the IP address of the specific host.
To allow connections from a specific network, use the permit host source-ip wildcard option. Replace source-ip with a network ID or the IP address of any host on the network that you want to specify. Replace wildcard with the dotted decimal notation for a mask that is the reverse of a subnet mask, where a 0 indicates a position that must be matched and a 1 indicates a position that does not matter. For instance, the wildcard 0.0.0.255 causes the last eight bits in the source IP address to be ignored. The permit 192.168.1.0 0.0.0.255 entry allows access from any host on the 192.168.1.0 network.
For extended IP ACLs, the wildcard parameter is required if the host keyword is not specified.
Use an extended access list to control connections based on the destination IP address or based on the protocol type. You can combine these conditions with information about the source IP address to create more restrictive conditions.
Table 3-1 lists the UDP keywords that you can use with extended access lists.
|
|
|
---|---|---|
Table 3-2 lists the TCP keywords that you can use with extended access lists.
|
|
|
---|---|---|
Table 3-3 lists the keywords that you can use to match specific ICMP message types and codes.
Examples
The following example shows how to create an access list on the WAAS device. You create this access list to allow the WAAS device to accept all web traffic that is redirected to it but limit host administrative access using SSH:
The following example shows how to activate the access list for an interface:
The following example shows how this configuration appears when you enter the show running-configuration command:
Related Commands
(config-ext-nacl) exit
To terminate extended ACL configuration mode and return to the global configuration mode, use the exit command.
Syntax Description
Defaults
Command Modes
Device Modes
Examples
The following example shows how to terminate extended ACL configuration mode and return to global configuration mode:
(config-ext-nacl) list
To display a list of specified entries within the extended ACL, use the list extended ACL configuration command.
list [ start-line-num [ end-line-num ]]
Syntax Description
Defaults
Command Modes
extended ACL configuration mode
Device Modes
Examples
The following example shows how to display a list of specified entries within the extended ACL:
Related Commands
(config-ext-nacl) move
To move a line to a new position within the extended ACL, use the move extended ACL configuration command.
move old-line-num new-line-num
Syntax Description
New position of the entry. The existing entry is moved to the following position in the access list. |
Defaults
Command Modes
extended ACL configuration mode
Device Modes
Examples
The following example shows how to move a line to a new position within the extended ACL:
Related Commands
(config-ext-nacl) permit
To add a line to an extended access list that specifies the type of packets that you want the WAAS device to accept for further processing, use the permit extended ACL configuration command. To add a condition to the extended ACL, note that the options depend on the chosen protocol.
For IP, use the following syntax to add a condition:
[ insert line-num ] permit { gre | icmp | tcp | udp | ip | proto-num } { source-ip [ wildcard ] |
host source-ip | any } { dest-ip [ wildcard ] | host dest-ip | any }
no permit { gre | icmp | tcp | udp | ip | proto-num } { source-ip [ wildcard ] | host source-ip | any } { dest-ip [ wildcard ] | host dest-ip | any }
For TCP, use the following syntax to add a condition:
[ insert line-num ] permit tcp { source-ip [ wildcard ] | host source-ip | any } [ operator port [ port ]] { dest-ip [ wildcard ] | host dest-ip | any } [ operator port [ port ]] [ established ]
no permit tcp { source-ip [ wildcard ] | host source-ip | any } [ operator port [ port ]]
{ dest-ip [ wildcard ] | host dest-ip | any } [ operator port [ port ]] [ established ]
For UDP, use the following syntax to add a condition:
[ insert line-num ] permit udp { source-ip [ wildcard ] | host source-ip | any } [ operator port [ port ]] { dest-ip [ wildcard ] | host dest-ip | any } [ operator port [ port ]]
no permit udp { source-ip [ wildcard ] | host source-ip | any } [ operator port [ port ]]
{ dest-ip [ wildcard ] | host dest-ip | any } [ operator port [ port ]]
For ICMP, use the following syntax to add a condition:
[ insert line-num ] permit icmp { source-ip [ wildcard ] | host source-ip | any } { dest-ip [ wildcard ] | host dest-ip | any } [ icmp-type [ code ] | icmp-msg ]
no permit icmp { source-ip [ wildcard ] | host source-ip | any } { dest-ip [ wildcard ] | host dest-ip | any } [ icmp-type [ code ] | icmp-msg ]
Syntax Description
Defaults
An access list drops all packets unless you configure at least one permit entry.
Command Modes
extended ACL configuration mode
Device Modes
Usage Guidelines
To create an entry, use a deny or permit keyword and specify the type of packets that you want the WAAS device to drop or to accept for further processing. By default, an access list denies everything because the list is terminated by an implicit deny any entry. You must include at least one permit entry to create a valid access list.
To allow connections from a specific host, use the permit host source-ip option and replace source-ip with the IP address of the specific host.
To allow connections from a specific network, use the permit host source-ip wildcard option. Replace source-ip with a network ID or the IP address of any host on the network that you want to specify. Replace wildcard with the dotted decimal notation for a mask that is the reverse of a subnet mask, where a 0 indicates a position that must be matched and a 1 indicates a position that does not matter. For instance, the wildcard 0.0.0.255 causes the last eight bits in the source IP address to be ignored. The permit 192.168.1.0 0.0.0.255 entry allows access from any host on the 192.168.1.0 network.
For extended IP ACLs, the wildcard parameter is required if the host keyword is not specified.
Use an extended access list to control connections based on the destination IP address or based on the protocol type. You can combine these conditions with information about the source IP address to create more restrictive condition.
Table 3-4 lists the UDP keywords that you can use with extended access lists.
|
|
|
---|---|---|
Table 3-5 lists the TCP keywords that you can use with extended access lists.
|
|
|
---|---|---|
Table 3-6 lists the keywords that you can use to match specific ICMP message types and codes.
Examples
The following example shows how to create an access list on the WAAS device. You create this access list to allow the WAAS device to accept all web traffic that is redirected to it but limit host administrative access using SSH:
The following example shows how to activate the access list for an interface:
The following example shows how this configuration appears when you enter the show running-configuration command: