An access control list (ACL) is a set of rules for identifying traffic based on criteria such as source IP address, destination IP address, and port number. The rules are also called permit or deny statements.

ACLs are primarily used for packet filtering. "Configuring packet filtering with ACLs" provides an example. You can use ACLs in QoS, security, routing, and other modules for identifying traffic. The packet drop or forwarding decisions depend on the modules that use ACLs.

ACL types

Type	ACL number	IP version	Match criteria
Basic ACLs	2000 to 2999	IPv4	Source IPv4 address.
Basic ACLs	2000 to 2999	IPv6	Source IPv6 address.
Advanced ACLs	3000 to 3999	IPv4	Source IPv4 address, destination IPv4 address, packet priority, protocol number, and other Layer 3 and Layer 4 header fields.
Advanced ACLs	3000 to 3999	IPv6	Source IPv6 address, destination IPv6 address, packet priority, protocol number, and other Layer 3 and Layer 4 header fields.
Layer 2 ACLs	4000 to 4999	IPv4 and IPv6	Layer 2 header fields, such as source and destination MAC addresses, 802.1p priority, and link layer protocol type.
User-defined ACLs	5000 to 5999	IPv4 and IPv6	User specified matching patterns in protocol headers.

Numbering and naming ACLs

When creating an ACL, you must assign it a number or name for identification. You can specify an existing ACL by its number or name. Each ACL type has a unique range of ACL numbers.

For an IPv4 basic or advanced ACL, its ACL number or name must be unique in IPv4. For an IPv6 basic or advanced ACL, its ACL number and name must be unique in IPv6. For a Layer 2 or user-defined ACL, its number or name must be globally unique.

Match order

The rules in an ACL are sorted in a specific order. When a packet matches a rule, the device stops the match process and performs the action defined in the rule. If an ACL contains overlapping or conflicting rules, the matching result and action to take depend on the rule order.

The following ACL match orders are available:

· config—Sorts ACL rules in ascending order of rule ID. A rule with a lower ID is matched before a rule with a higher ID. If you use this method, check the rules and their order carefully.

NOTE:

The match order of user-defined ACLs can only be config.

· auto—Sorts ACL rules in depth-first order. Depth-first ordering makes sure any subset of a rule is always matched before the rule. Table 1 lists the sequence of tie breakers that depth-first ordering uses to sort rules for each type of ACL.

Table 1 Sort ACL rules in depth-first order

ACL type	Sequence of tie breakers
IPv4 basic ACL	1. VPN instance. 2. More 0s in the source IPv4 address wildcard (more 0s means a narrower IPv4 address range). 3. Rule configured earlier.
IPv4 advanced ACL	1. VPN instance. 2. Specific protocol number. 3. More 0s in the source IPv4 address wildcard mask. 4. More 0s in the destination IPv4 address wildcard. 5. Narrower TCP/UDP service port number range. 6. Rule configured earlier.
IPv6 basic ACL	1. VPN instance. 2. Longer prefix for the source IPv6 address (a longer prefix means a narrower IPv6 address range). 3. Rule configured earlier.
IPv6 advanced ACL	1. VPN instance. 2. Specific protocol number. 3. Longer prefix for the source IPv6 address. 4. Longer prefix for the destination IPv6 address. 5. Narrower TCP/UDP service port number range. 6. Rule configured earlier.
Layer 2 ACL	1. More 1s in the source MAC address mask (more 1s means a smaller MAC address). 2. More 1s in the destination MAC address mask. 3. Rule configured earlier.

A wildcard mask, also called an inverse mask, is a 32-bit binary number represented in dotted decimal notation. In contrast to a network mask, the 0 bits in a wildcard mask represent "do care" bits, and the 1 bits represent "don't care" bits. If the "do care" bits in an IP address are identical to the "do care" bits in an IP address criterion, the IP address matches the criterion. All "don't care" bits are ignored. The 0s and 1s in a wildcard mask can be noncontiguous. For example, 0.255.0.255 is a valid wildcard mask.

Rule numbering

ACL rules can be manually numbered or automatically numbered. This section describes how automatic ACL rule numbering works.

Rule numbering step

If you do not assign an ID to the rule you are creating, the system automatically assigns it a rule ID. The rule numbering step sets the increment by which the system automatically numbers rules. For example, the default ACL rule numbering step is 5. If you do not assign IDs to rules you are creating, they are automatically numbered 0, 5, 10, 15, and so on. The wider the numbering step, the more rules you can insert between two rules.

By introducing a gap between rules rather than contiguously numbering rules, you have the flexibility of inserting rules in an ACL. This feature is important for a config-order ACL, where ACL rules are matched in ascending order of rule ID.

Automatic rule numbering and renumbering

The ID automatically assigned to an ACL rule takes the nearest higher multiple of the numbering step to the current highest rule ID, starting with 0.

For example, if the step is 5, and there are five rules numbered 0, 5, 9, 10, and 12, the newly defined rule is numbered 15. If the ACL does not contain a rule, the first rule is numbered 0.

Whenever the step changes, the rules are renumbered, starting from 0. For example, changing the step from 5 to 2 renumbers rules 5, 10, 13, and 15 as rules 0, 2, 4, and 6.

Fragment filtering with ACLs

Traditional packet filtering matches only first fragments of packets, and allows all subsequent non-first fragments to pass through. Attackers can fabricate non-first fragments to attack networks.

To avoid risks, the ACL feature is designed as follows:

· Filters all fragments by default, including non-first fragments.

· Allows for matching criteria modification for efficiency. For example, you can configure the ACL to filter only non-first fragments.

Configuration restrictions and guidelines

Follow these restrictions and guidelines when you configure an ACL:

· If you create a numbered ACL, you can enter the view of the ACL by using either of the following commands:

¡ acl [ ipv6 ] number acl-number.

¡ acl { [ ipv6 ] { advanced | basic } | mac | user-defined } acl-number.

· If you create a named non-WLAN ACL by using the acl [ ipv6 ] number acl-number name acl-name command, you can enter the view of the ACL by using either of the following commands:

¡ acl [ ipv6 ] number acl-number [ name acl-name ].

¡ acl { [ ipv6 ] { advanced | basic } | mac | user-defined } name acl-name.

· If you create a named ACL by using the acl { [ ipv6 ] { advanced | basic } | mac | user-defined } name acl-name command, you can enter the view of the ACL by using only the command that is used to create the ACL.

· The device uses the slow forwarding process for a packet if the packet matches an ACL rule that contains criteria except for the following ones:

¡ Source IP address, source port number, destination IP address, destination port number, or transport layer protocol.

¡ ICMP message type or ICMP message code.

¡ VPN instance.

¡ Logging operation.

¡ Time range.

During the slow forwarding process, the device sends the matching packets to the control plane. The forwarding performance is downgraded.

Configuration task list

Tasks at a glance
(Required.) Configure ACLs according to the characteristics of the packets to be matched: · Configuring a basic ACL ¡ Configuring an IPv4 basic ACL ¡ Configuring an IPv6 basic ACL · Configuring an advanced ACL ¡ Configuring an IPv4 advanced ACL ¡ Configuring an IPv6 advanced ACL · Configuring a Layer 2 ACL · Configuring a user-defined ACL
(Optional.) Copying an ACL
(Optional.) Configuring packet filtering with ACLs

Configuring a basic ACL

This section describes procedures for configuring IPv4 and IPv6 basic ACLs.

Configuring an IPv4 basic ACL

IPv4 basic ACLs match packets based only on source IP addresses.

To configure an IPv4 basic ACL:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an IPv4 basic ACL and enter its view.	acl basic { acl-number \| name acl-name } [ match-order { auto \| config } ] acl number acl-number [ name acl-name ] [ match-order { auto \| config } ]	By default, no ACLs exist. The value range for a numbered IPv4 basic ACL is 2000 to 2999. Use the acl number acl-number or acl basic acl-number command to create a numbered IPv4 basic ACL. To enter the view of a named IPv4 basic ACL, use the acl name acl-name or acl basic name acl-name command. The acl name acl-name command supports entering the view of an existing IPv4 basic and advanced ACL. To enter the view of a numbered IPv4 basic ACL, use the acl number acl-number or acl basic acl-number command.
3. (Optional.) Configure a description for the IPv4 basic ACL.	description text	By default, an IPv4 basic ACL does not have a 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 } [ counting \| fragment \| [ flow-logging \| logging ] \| source { source-address source-wildcard \| any } \| time-range time-range-name \| vpn-instance vpn-instance-name ] *	By default, no IPv4 basic ACL rules exist. The flow-logging and logging keywords take effect only when the module (for example, packet filtering) that uses the ACL supports logging. The vpn-instance vpn-instance-name option is not supported in the outbound direction.
6. (Optional.) Add or edit a rule comment.	rule rule-id comment text	By default, no rule comment is configured.

Configuring an IPv6 basic ACL

IPv6 basic ACLs match packets based only on source IP addresses.

To configure an IPv6 basic ACL:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an IPv6 basic ACL view and enter its view.	acl ipv6 basic { acl-number \| name acl-name } [ match-order { auto \| config } ] acl ipv6 number acl-number [ name acl-name ] [ match-order { auto \| config } ]	By default, no ACLs exist. The value range for a numbered IPv6 basic ACL is 2000 to 2999. Use the acl ipv6 number acl-number or acl ipv6 basic acl-number command to create a numbered IPv6 basic ACL. To enter the view of a named IPv6 basic ACL, use the acl ipv6 name acl-name or acl ipv6 basic name acl-name command. The acl ipv6 name acl-name command supports entering the view of an existing IPv6 basic and advanced ACL. To enter the view of a numbered IPv6 basic ACL, use the acl ipv6 number acl-number or acl ipv6 basic acl-number command.
3. (Optional.) Configure a description for the IPv6 basic ACL.	description text	By default, an IPv6 basic ACL does not have a 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 } [ counting \| [ flow-logging \| logging ] \| routing \| source { source-address source-prefix \| source-address/source-prefix \| any } \| time-range time-range-name \| vpn-instance vpn-instance-name ] *	By default, no IPv6 basic ACL rules exist. The flow-logging and logging keywords take effect only when the module (for example, packet filtering) that uses the ACL supports logging. If an IPv6 basic ACL is used for outbound QoS traffic classification or outbound packet filtering, do not specify the routing keyword. The vpn-instance vpn-instance-name option is not supported in the outbound direction.
6. (Optional.) Add or edit a rule comment.	rule rule-id comment text	By default, no rule comment is 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 advanced { acl-number \| name acl-name } [ match-order { auto \| config } ] acl number acl-number [ name acl-name ] [ match-order { auto \| config } ]	By default, no ACLs exist. The value range for a numbered IPv4 advanced ACL is 3000 to 3999. Use the acl number acl-number or acl advanced acl-number command to create a numbered IPv4 advanced ACL. To enter the view of a named IPv4 advanced ACL, use the acl name acl-name or acl advanced name acl-name command t. The acl name acl-name command supports entering the view of an existing IPv4 basic and advanced ACL. To enter the view of a numbered IPv4 advanced ACL, use the acl number acl-number or acl advanced acl-number command.
3. (Optional.) Configure a description for the IPv4 advanced ACL.	description text	By default, an IPv4 advanced ACL does not have a 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 fin-value \| psh psh-value \| rst rst-value \| syn syn-value \| urg urg-value } * \| established } \| counting \| destination { object-group address-group-name \| dest-address dest-wildcard \| any } \| destination-port operator port1 [ port2 ] \| { dscp dscp \| { precedence precedence \| tos tos } * } \| fragment \| icmp-type { icmp-type [ icmp-code ] \| icmp-message } \| [ flow-logging \| logging ] \| qos-local-id local-id-value \| source { source-address source-wildcard \| any } \| source-port operator port1 [ port2 ] \| time-range time-range-name \| vpn-instance vpn-instance-name ] *	By default, no IPv4 advanced ACL rules exist. The flow-logging and logging keywords take effect only when the module (for example, packet filtering) that uses the ACL supports logging. If an IPv4 advanced ACL is used for outbound QoS traffic classification or outbound packet filtering, do not specify the qos-local-id local-id-value option. The vpn-instance vpn-instance-name option is not supported in the outbound direction.
6. (Optional.) Add or edit a rule comment.	rule rule-id comment text	By default, no rule comment is configured.

Configuring an IPv6 advanced ACL

IPv6 advanced ACLs match packets based on the following criteria:

· Source IPv6 addresses.

· Destination IPv6 addresses.

· Packet priorities.

· Protocol numbers.

· Other protocol header fields such as the TCP/UDP source port number, TCP/UDP destination port number, ICMPv6 message type, and ICMPv6 message code.

Compared to IPv6 basic ACLs, IPv6 advanced ACLs allow more flexible and accurate filtering.

To configure an IPv6 advanced ACL:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an IPv6 advanced ACL and enter its view.	acl ipv6 advanced { acl-number \| name acl-name } [ match-order { auto \| config } ] acl ipv6 number acl-number [ name acl-name ] [ match-order { auto \| config } ]	By default, no ACLs exist. The value range for a numbered IPv6 advanced ACL is 3000 to 3999. Use the acl ipv6 number acl-number or acl ipv6 advanced acl-number command to create a numbered IPv6 advanced ACL. To enter the view of a named IPv6 advanced ACL, use the acl ipv6 name acl-name or acl ipv6 advanced name acl-name command. The acl ipv6 name acl-name command supports entering the view of an existing IPv6 basic and advanced ACL. To enter the view of a numbered IPv6 advanced ACL, use the acl ipv6 number acl-number or acl ipv6 advanced acl-number command.
3. (Optional.) Configure a description for the IPv6 advanced ACL.	description text	By default, an IPv6 advanced ACL does not have a 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 fin-value \| psh psh-value \| rst rst-value \| syn syn-value \| urg urg-value } * \| established } \| counting \| destination { dest-address dest-prefix \| dest-address/dest-prefix \| any } \| destination-port operator port1 [ port2 ] \| dscp dscp \| flow-label flow-label-value \| icmp6-type { icmp6-type icmp6-code \| icmp6-message } \| [ flow-logging \| logging ] \| qos-local-id local-id-value \| routing \| hop-by-hop [ type hop-type ] \| source { source-address source-prefix \| source-address/source-prefix \| any } \| source-port operator port1 [ port2 ] \| time-range time-range-name \| vpn-instance vpn-instance-name ] *	By default, no IPv6 advanced ACL rules exist. The flow-logging and logging keywords take effect only when the module (for example, packet filtering) that uses the ACL supports logging. If an IPv6 advanced ACL is used for outbound QoS traffic classification or outbound packet filtering, do not specify the qos-local-id local-id-value, routing, or hop-by-hop parameter. The vpn-instance vpn-instance-name option is not supported in the outbound direction.
6. (Optional.) Add or edit a rule comment.	rule rule-id comment text	By default, no rule comment is configured.

Configuring a Layer 2 ACL

Layer 2 ACLs, also called Ethernet frame header ACLs, match packets based on Layer 2 Ethernet header fields, such as:

· Source MAC address.

· Destination MAC address.

· 802.1p priority (VLAN priority).

· Link layer protocol type.

To configure a Layer 2 ACL:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a Layer 2 ACL and enter its view.	acl mac { acl-number \| name acl-name } [ match-order { auto \| config } ] acl number acl-number [ name acl-name ] [ match-order { auto \| config } ]	By default, no ACLs exist. The value range for a numbered Layer 2 ACL is 4000 to 4999. Use the acl number acl-number or acl mac acl-number command to create a numbered Layer 2 ACL. Use the acl number acl-number or acl mac acl-number command to enter the view of a numbered Layer 2 ACL. Use the acl mac name acl-name command to enter the view of a named Layer 2 ACL.
3. (Optional.) Configure a description for the Layer 2 ACL.	description text	By default, a Layer 2 ACL does not have a 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 } [ cos dot1p \| counting \| dest-mac dest-address dest-mask \| { lsap lsap-type lsap-type-mask \| type protocol-type protocol-type-mask } \| source-mac source-address source-mask \| time-range time-range-name ] *	By default, no Layer 2 ACL rules exist.
6. (Optional.) Add or edit a rule comment.	rule rule-id comment text	By default, no rule comment is configured.

Configuring a user-defined ACL

User-defined ACLs allow you to customize rules based on information in protocol headers. You can define a user-defined ACL to match packets. A specific number of bytes after an offset (relative to the specified header) are compared against a match pattern after being ANDed with a match pattern mask.

To configure a user-defined ACL:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a user-defined ACL and enter its view.	acl user-defined { acl-number \| name acl-name } acl number acl-number [ name acl-name ]	By default, no ACLs exist. The value range for a numbered user-defined ACL is 5000 to 5999. Use the acl number acl-number or acl user-defined acl-number command to create a numbered user-defined ACL. Use the acl number acl-number or acl user-defined acl-number command to enter the view of a numbered user-defined ACL. Use the acl user-defined name acl-name command to enter the view of a named user-defined ACL.
3. (Optional.) Configure a description for the user-defined ACL.	description text	By default, a user-defined ACL does not have a description.
4. Create or edit a rule.	rule [ rule-id ] { deny \| permit } [ { l2 rule-string rule-mask offset }&<1-8> ] [ counting \| time-range time-range-name ] *	By default, no user-defined ACL rules exist.
5. (Optional.) Add or edit a rule comment.	rule rule-id comment text	By default, no rule comment is configured.

Copying an ACL

You can create an ACL by copying an existing ACL (source ACL). The new ACL (destination ACL) has the same properties and content as the source ACL, but uses a different number or name than the source ACL.

To successfully copy an ACL, make sure:

· The destination ACL number is from the same type as the source ACL number.

· The source ACL already exists, but the destination ACL does not.

To copy an ACL:

Step	Command
1. Enter system view.	system-view
2. Copy an existing ACL to create a new ACL.	acl [ ipv6 \| mac \| user-defined ] copy { source-acl-number \| name source-acl-name } to { dest-acl-number \| name dest-acl-name }

Configuring packet filtering with ACLs

This section describes procedures for using an ACL to filter packets. For example, you can apply an ACL to an interface to filter incoming or outgoing packets.

Applying an ACL to an interface for packet filtering

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
3. Apply an ACL to the interface to filter packets.	packet-filter [ ipv6 \| mac \| user-defined ] { acl-number \| name acl-name } { inbound \| outbound } [ hardware-count ]	By default, an interface does not filter packets.

Configuring the applicable scope of packet filtering on a VLAN interface

You can configure the packet filtering on a VLAN interface to filter the following packets:

· Packets forwarded at Layer 3 by the VLAN interface.

· All packets, including packets forwarded at Layer 3 by the VLAN interface and packets forwarded at Layer 2 by the physical ports associated with the VLAN interface.

To configure the applicable scope of packet filtering on a VLAN interface:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a VLAN interface and enter its view.	interface vlan-interface vlan-interface-id	If the VLAN interface already exists, you directly enter its view. By default, no VLAN interface exists.
3. Specify the applicable scope of packet filtering on the VLAN interface.	packet-filter filter { route \| all }	By default, the packet filtering filters packets forwarded at Layer 3.

Configuring logging and SNMP notifications for packet filtering

You can configure the ACL module to generate log entries or SNMP notifications for packet filtering and output them to the information center or SNMP module at the output interval. The log entry or notification records the number of matching packets and the matched ACL rules. If an ACL is matched for the first time, the device immediately outputs a log entry or notification to record the matching packet.

For more information about the information center and SNMP, see Network Management and Monitoring Configuration Guide.

To configure logging and SNMP notifications for packet filtering:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the interval for outputting packet filtering logs or notifications.	acl { logging \| trap } interval interval	The default setting is 0 minutes. By default, the device does not generate log entries or SNMP notifications for packet filtering.

Setting the packet filtering default action

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the packet filtering default action to deny.	packet-filter default deny	By default, the packet filter permits packets that do not match any ACL rule to pass.

Displaying and maintaining ACLs

Execute display commands in any view and reset commands in user view.

Task	Command
Display ACL configuration and match statistics.	display acl [ ipv6 \| mac \| user-defined ] { acl-number \| all \| name acl-name }
Display ACL application information for packet filtering.	display packet-filter { interface [ interface-type interface-number ] [ inbound \| outbound ] \| interface vlan-interface vlan-interface-number [ inbound \| outbound ] [ slot slot-number ] }
Display match statistics and default action statistics for packet filtering ACLs.	display packet-filter statistics interface interface-type interface-number { inbound \| outbound } [ [ ipv6 \| mac \| user-defined ] { acl-number \| name acl-name } ] [ brief ]
Display the accumulated statistics for packet filtering ACLs.	display packet-filter statistics sum { inbound \| outbound } [ ipv6 \| mac \| user-defined ] { acl-number \| name acl-name } [ brief ]
Display detailed ACL packet filtering information.	display packet-filter verbose interface interface-type interface-number { inbound \| outbound } [ [ ipv6 \| mac \| user-defined ] { acl-number \| name acl-name } ] [ slot slot-number ]
Display QoS and ACL resource usage.	display qos-acl resource [ slot slot-number ]
Clear ACL statistics.	reset acl [ ipv6 \| mac \| user-defined ] counter { acl-number \| all \| name acl-name }
Clear match statistics, accumulated match statistics, and default action statistics for packet filtering ACLs.	reset packet-filter statistics interface [ interface-type interface-number ] { inbound \| outbound } [ [ ipv6 \| mac \| user-defined ] { acl-number \| name acl-name } ]

ACL configuration examples

Interface-based packet filtering configuration example

Network requirements

A company interconnects its departments through the device. Configure packet filtering to:

· Permit access from the President's office at any time to the financial database server.

· Permit access from the Finance department to the financial database server only during working hours (from 8:00 to 18:00) on working days.

· Deny access from any other department to the financial database server.

Figure 1 Network diagram

Configuration procedure

# Create a periodic time range from 8:00 to 18:00 on working days.

<Device> system-view

[Device] time-range work 08:0 to 18:00 working-day

# Create an IPv4 advanced ACL numbered 3000.

[Device] acl advanced 3000

# Configure a rule to permit access from the President's office to the financial database server.

[Device-acl-ipv4-adv-3000] rule permit ip source 192.168.1.0 0.0.0.255 destination 192.168.0.100 0

# Configure a rule to permit access from the Finance department to the financial database server during working hours.

[Device-acl-ipv4-adv-3000] rule permit ip source 192.168.2.0 0.0.0.255 destination 192.168.0.100 0 time-range work

# Configure a rule to deny access to the financial database server.

[Device-acl-ipv4-adv-3000] rule deny ip source any destination 192.168.0.100 0

[Device-acl-ipv4-adv-3000] quit

# Apply IPv4 advanced ACL 3000 to filter outgoing packets on interface Ten-GigabitEthernet 1/1/1.

[Device] interface ten-gigabitethernet 1/1/1

[Device-Ten-GigabitEthernet1/1/1] packet-filter 3000 outbound

[Device-Ten-GigabitEthernet1/1/1] quit

Verifying the configuration

# Verify that a PC in the Finance department can ping the financial database server during working hours. (All PCs in this example use Windows XP).

C:\> ping 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:

Reply from 192.168.0.100: bytes=32 time=1ms TTL=255

Reply from 192.168.0.100: bytes=32 time<1ms TTL=255

Ping statistics for 192.168.0.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 1ms, Average = 0ms

# Verify that a PC in the Marketing department cannot ping the financial database server during working hours.

C:\> ping 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:

Request timed out.

Ping statistics for 192.168.0.100:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

# Display configuration and match statistics for IPv4 advanced ACL 3000 on the device during the working hours.

[Device] display acl 3000

Advanced ACL 3000, named -none-, 3 rules,

ACL's step is 5

rule 0 permit ip source 192.168.1.0 0.0.0.255 destination 192.168.0.100 0

rule 5 permit ip source 192.168.2.0 0.0.0.255 destination 192.168.0.100 0 time-range work (Active)

rule 10 deny ip destination 192.168.0.100 0

The output shows that rule 5 is active.

09-ACL and QoS Configuration Guide

ACL types

Numbering and naming ACLs

Rule numbering step

Automatic rule numbering and renumbering

Fragment filtering with ACLs

Configuration restrictions and guidelines

Configuration task list

Configuring a basic ACL

Configuring a Layer 2 ACL

Configuring a user-defined ACL

Copying an ACL

Configuring packet filtering with ACLs

ACL configuration examples

Interface-based packet filtering configuration example

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

Company Information

News & Events

Contact Us