5
Step Command Remarks
[
counting
|
fragment
|
logging
|
routing
[
type
routing-type ] |
source
{ source-address
source-prefix |
source-address/source-prefix |
any
} |
time-range
time-range-name |
vpn-instance
vpn-instance-name ] *
does not contain any rule.
The
logging
keyword takes effect
only when the module (for
example, packet filtering) that
uses the ACL supports logging.
If an ACL is for QoS traffic
classification or packet filtering:
• Do not specify the fragment
keyword.
• Do not specify the
vpn-instance or routing
keyword if the ACL is for
outbound application.
6. (Optional.) Add or edit a rule
comment.
rule
rule-id
comment
text
By default, no rule comments are
configured.
Configuring an advanced ACL
This section describes procedures for configuring IPv4 and IPv6 advanced ACLs.
Configuring an IPv4 advanced ACL
IPv4 advanced ACLs match packets based on the following criteria:
• Source IP addresses.
• Destination IP addresses.
• Packet priorities.
• Protocol numbers.
• Other protocol header information, such as TCP/UDP source and destination port numbers,
TCP flags, ICMP message types, and ICMP message codes.
Compared to IPv4 basic ACLs, IPv4 advanced ACLs allow more flexible and accurate filtering.
To configure an IPv4 advanced ACL:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Create an IPv4 advanced
ACL and enter its view.
acl number
acl-number [
name
acl-name ] [
match-order
{
auto
|
config
} ]
By default, no ACL exists.
IPv4 advanced ACLs are
numbered in the range of 3000 to
3999.
You can use the
acl
name
acl-name command to enter the
view of a named ACL.
3. (Optional.) Configure a
description for the IPv4
advanced ACL.
description
text
By default, an IPv4 advanced ACL
has no ACL description.
4. (Optional.) Set the rule
numbering step.
step
step-value
The default setting is 5.
5. Create or edit a rule.
rule
[ rule-id ] {
deny
|
permit
}
protocol [ { {
ack
ack-value |
fin
By default, an IPv4 advanced ACL
does not contain any rule.
To Next Page
Loading...
Need help?
General