User's Manual

Chapter 3 - Operation and Administration Using the CLI NPU Configuration
4Motion 177 System Manual
3.3.10.1.2 Configuring ACLs in the Standard Mode
After you have enabled the standard ACL configuration mode, you can create or
delete the Permit/Deny rules for forwarding traffic from/to a particular
source/destination IP address.
This section describes the commands for:
 “Creating a Permit/Deny Rule (Standard Mode)” on page 177
 “Deleting a Permit/Deny Rule (Standard Mode)” on page 179
3.3.10.1.2.1 Creating a Permit/Deny Rule (Standard Mode)
Run the following commands to create the Permit/Deny rules for forwarding
traffic from/to a particular source/destination IP address:
npu(config-std-nacl)# permit {any | host <src-ip-address> |
<network-src-ip> <mask>} [{any | host <dest-ip-address> |
<network-dest-ip> <mask>}]
npu(config-std-nacl)# deny {any | host <src-ip-address> |
<network-src-ip> <mask>} [{any | host <dest-ip-address> |
<network-dest-ip> <mask>}]
The following table lists the parameters and their descriptions in these
commands.
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.
IMPORTANT
In the above commands, it is mandatory to specify the source IP address for which the Permit/Deny
rule is to be created. If you do not specify the destination IP address/subnet mask, by default, traffic
to all destination IP addresses configured for the NPU is permitted/denied.