Established Flag; Configuring Layer 2 And Layer 3 Acls On An Interface - Dell Force10 S4810P Configuration Manual

FTOS(config-ext-nacl)#show config
!
ip access-list extended nimule
seq 5 deny tcp host 123.55.34.0 any
seq 10 permit udp 154.44.0.0 0.0.255.255 host 34.6.0.0
FTOS(config-ext-nacl)#
To view all configured IP ACLs and the number of packets processed through the ACL, use the
accounting access-list
a standard IP

Established Flag

The (established) flag is deprecated for Terascale series line cards.The flag is only available on legacy
est
EtherScale linecards. Employ the
To obtain the functionality of
• permit tcp any any rst
• permit tcp any any ack

Configuring Layer 2 and Layer 3 ACLs on an Interface

Both Layer 2 and Layer 3 ACLs may be configured on an interface in Layer 2 mode. If both L2 and L3
ACLs are applied to an interface, the following rules apply:
• The packets routed by FTOS are governed by the L3 ACL only, since they are not filtered against an
L2 ACL.
• The packets switched by FTOS are first filtered by the L3 ACL, then by the L2 ACL.
• 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
• L3 Egress Access list
• L2 Egress Access list
If a rule is simply appended, existing counters are not affected.
Table 7-2. L2 and L3 ACL Filtering on Switched Packets
L2 ACL Behavior
Deny
Deny
116
| Access Control Lists (ACLs)
command in the EXEC Privilege mode as shown in the first example in
ACL.
ack
use the following ACLs:
est,
L3 ACL Behavior
Deny
Permit
and flags instead to achieve the same functionality.
rst
Decision on Targeted Traffic
Denied by L3 ACL
Permitted by L3 ACL
show ip
Configure