Dell S6000 FTOS 9.0(2.0) Configuration Guide for the System - Page 97

• When packets are switched by FTOS, the egress L3 ACL does not filter the packet. For the following features, if counters are enabled on rules that have already been configured and a new rule is either inserted or prepended, all the existing counters will be reset: • L2 Ingress Access list • L2 Egress Access list If a rule is simply appended, existing counters are not affected. Table 6-1. L2 and L3 ACL Filtering on Switched Packets L2 ACL Behavior Deny Deny Permit Permit L3 ACL Behavior Deny Permit Deny Permit Decision on Targeted Traffic Denied by L3 ACL Permitted by L3 ACL Denied by L3 ACL Permitted by L3 ACL Note: If an interface is configured as a "vlan-stack access" port, the packets are filtered by an L2 ACL only. The L3 ACL applied to such a port does not affect traffic. That is, existing rules for other features (such as trace-list, PBR, and QoS) are applied accordingly to the permitted traffic. For information on MAC ACLs, refer to Chapter 26, Layer 2. Assign an IP ACL to an Interface s Ingress IP ACLs are supported on platforms: z Ingress and Egress IP ACL are supported on platforms: z To pass traffic through a configured IP ACL, you must assign that ACL to a physical interface, a port channel interface, or a VLAN. The IP ACL is applied to all traffic entering a physical or port channel interface and the traffic is either forwarded or dropped depending on the criteria and actions specified in the ACL. The same ACL may be applied to different interfaces and that changes its functionality. For example, you can take ACL "ABCD" and apply it using the in keyword and it becomes an ingress access list. If you apply the same ACL using the out keyword, it becomes an egress access list. If you apply the same ACL to the loopback interface, it becomes a loopback access list. This chapter covers the following topics: • Configuring Ingress ACLs • Configuring Egress ACLs Access Control Lists (ACLs) | 75