1.1 67.access Control Lists Overview
1.1 67.access Control Lists Overview
• Standard ACL - It can permit orc deny traffic based only on the source
address field of the packet.
.5 .5 .5
192.1.12.0/24 192.1.23.0/24
R1 R2 R3
Standard ACL Examples:
Example#1: Blocking the 192.1.10.0/24 network from Accessing the 192.1.30.0/24 using an
Numbered ACL. Permit the rest of the traffic.
Access-list 1 deny 192.1.10.0 0.0.0.255
Access-list 1 permit any
!
c
Interface E 0/1
ip access-group 1 out
Example#2: Blocking the host 192.1.10.5/24 network from Accessing the 192.1.20.0/24
using an Named ACL. Permit the rest of the traffic.
Ip access-list standard ACL-1
deny host 192.1.10.5
permit any
!
Interface E 0/2
ip access-group ACL-1 out
Extended ACLs
Extended ACLs are used to filter traffic by matching traffic based on following:
• Source / Destination IP Address Field
• Protocol : TCP/UDP/ICMP
• Application Protocol / Port Numbers : WWW [80], Telnet [23], DNS [53]
c
Extended ACLs can either be Numbered or Named.
Numbered ACLs uses numbers between (100 – 199) or (2000 – 2699).
Named ACLs uses names to identify the ACLs.
Just like the Standard ACL, the Extended ACLs also have an implicit “Deny”
statement at the end of each ACL.
The implicit deny statement will use the Protocol as IP to indicate all protocols,
“any” to indicate any source and a “any” to indicate any destination.
The implicit Deny statement for extended is “Deny IP any any”.
Network Diagram:
192.1.10.0/24 192.1.20.0/24 192.1.30.0/24
.5 .5 .5
192.1.12.0/24 192.1.23.0/24
R1 R2 R3
Extended ACL Examples:
Example#1: Blocking the 192.1.10.0/24 network from Accessing the 192.1.20.0/24 &
192.1.30.0/24 networks for Telnet and ICMP using an Numbered ACL. Permit the rest of the
traffic. Configure R1 for the block.