User's Manual

Chapter 3 - Operation and Administration Using the CLI NPU Configuration
4Motion 180 System Manual
3.3.10.1.3 Configuring ACLs in the Extended Mode
After you have enabled the extended ACL configuration mode, you can create
Permit/Deny rules based on source/destination IP address, protocol and
source/destination port numbers.
This section describes the commands to be used for:
 “Configuring Permit/Deny Rules from/to a Specific Protocol and
Source/Destination IP Addresses” on page 181
 “Configuring Permit/Deny Rules for TCP/UDP Traffic” on page 185
 “Configuring Permit/Deny Rules for ICMP Traffic” on page 194
Syntax
Description
Parameter Description Presence Default
Value
Possible
Values
{ any | host
<src-ip-addres
s> |
<network-src-i
p> <mask> }
Indicates the source IP
address/subnet for which the
Permit/Deny rule is to be
deleted.
Mandatory N/A For details,
refer
Table 3-19
[ { any |
host
<dest-ip-addre
ss> |
<network-dest-
ip> <mask> } ]
Indicates the destination IP
address/subnet for which the
Permit/Deny rule is to be
deleted.
Optional any For details,
refer
Table 3-19
Command
Modes
Standard ACL configuration mode
IMPORTANT
You cannot create Permit or Deny rules for an ACL that is associated with a Qos marking rule. You
can either associate QoS marking rules or permit/deny rules with an ACL.
IMPORTANT
After you have configured the rules to be applied on an ACL, you can attach the ACL to the NPU or
AUs. The ACL enables filtering of traffic destined to these interfaces. For more information, refer to
Section 3.3.10.3.