Configuring An Advanced Acl; Configuring An Ipv4 Advanced Acl - HP 6125XLG Configuration Manual

Step
1. Enter system view.
2. Create an IPv6 basic ACL
view and enter its view.
3. (Optional.) Configure a
description for the IPv6 basic
ACL.
4. (Optional.) Set the rule
numbering step.
5. Create or edit a rule.
6. (Optional.) Add or edit a rule
comment.

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 source IP addresses, destination IP addresses, packet
priorities, protocols over IP, and 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
1. Enter system view.
Command
system-view
acl ipv6 number acl-number
[ name acl-name ] [ match-order
{ auto | config } ]
description text
step step-value
rule [ rule-id ] { deny | permit }
[ 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 ] *
rule rule-id comment text
Command
system-view
5
Remarks
N/A
By default, no ACL exists.
IPv6 basic ACLs are numbered in
the range of 2000 to 2999.
You can use the acl ipv6 name
acl-name command to enter the
view of a named ACL.
By default, an IPv6 basic ACL has
no ACL description.
The default setting is 5.
By default, an IPv6 basic ACL 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 IPv6 basic ACL is for QoS
traffic classification or packet
filtering, do not specify the
vpn-instance or fragment
keyword, and do not specify the
routing keyword for outbound
traffic.
By default, no rule comments are
configured.
Remarks
N/A