An extended access control list (ACL) allows more granular control over network traffic by checking both source and destination addresses, as well as protocols, port numbers, and other packet details. There are three basic steps to configure an extended ACL: 1) create an ACL entry with the access-list command, 2) apply the ACL to an interface with ip access-group, and 3) activate the ACL on that interface. Extended ACLs provide administrators flexibility to permit or deny traffic based on specific matches.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
224 views
Ex 20 EACL
An extended access control list (ACL) allows more granular control over network traffic by checking both source and destination addresses, as well as protocols, port numbers, and other packet details. There are three basic steps to configure an extended ACL: 1) create an ACL entry with the access-list command, 2) apply the ACL to an interface with ip access-group, and 3) activate the ACL on that interface. Extended ACLs provide administrators flexibility to permit or deny traffic based on specific matches.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4
Ex 20: Extended ACL
Three basic steps to configure Extended Access List
Use the access-list global configuration command to create an entry in a Extended ACL. Use the interface configuration command to select an interface to which to apply the ACL. Use the ip access-group interface configuration command to activate the existing ACL on an interface. An extended ACL gives you much more power than just a standard ACL. Extended IP ACLs check both the source and destination packet addresses. They can also check for specific protocols, port numbers, and other parameters, which allow administrators more flexibility and control.
Command Parameters Descriptions access-list Main command access-list-number Identifies the list using a number in the ranges of 100199 or 2000 2699. permit | deny Indicates whether this entry allows or blocks the specified address. protocol IP, TCP, UDP, ICMP, GRE, or IGRP. source and destination Identifies source and destination IP addresses. source-wildcard and destination-wildcard The operator can be lt (less than), gt (greater than), eq (equal to), or neq (not equal to). The port number referenced can be either the source port or the destination port, depending on where in the ACL the port number is configured. As an alternative to the port number, well-known application names can be used, such as Telnet, FTP, and SMTP. established For inbound TCP only. Allows TCP traffic to pass if the packet is a response to an outbound-initiated session. This type of traffic has the acknowledgement (ACK) bits set. (See the Extended ACL with the Established Parameter example.) log Sends a logging message to the console.
Well-Known Port Numbers and IP Protocols Port Number IP Protocol 20 (TCP) FTP data 21 (TCP) FTP control 23 (TCP) Telnet 25 (TCP) Simple Mail Transfer Protocol (SMTP) 53 (TCP/UDP) Domain Name System (DNS) 69 (UDP) TFTP 80 (TCP) HTTP With Access Lists you will have a variety of uses for the wild card masks, but typically For CCNA exam prospective you should be able to do following: Block host to host Block host to network Block Network to network Block telnet access for critical resources of company Limited ftp access for user Stop exploring of private network form ping Limited web access Configure established keyword Block host to host Task You are the network administrator at ComputerNetworkingNotes.com. Your company hire a new employee and give him a pc 10.0.0.3. your company's critical record remain in 40.0.0.3. so you are asked to block the access of 40.0.0.3 from 10.0.0.3. while 10.0.0.3 must be able connect with other computers of network to perfom his task. Decide where to apply ACL and in which directions. As we are configuring Extended access list. With extended access list we can filter the packed as soon as it genrate. So we will place our access list on F0/0 of Router1841 the nearest port of 10.0.0.3 To configure Router1841 (Hostname R1) double click on it and select CLI R1>enable R1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. R1(config)#access-list 101 deny ip host 10.0.0.3 40.0.0.3 0.0.0.0 R1(config)#access-list 101 permit ip any any R1(config)#interface fastEthernet 0/0 R1(config-if)#ip access-group 101 in R1(config-if)#exit R1(config)# Verify by doing ping from 10.0.0.3 to 40.0.0.3. It should be reqest time out. Also ping other computers of network including 40.0.0.2. ping shuld be sucessfully. Block host to network Task Now we will block the 10.0.0.3 from gaining access on the network 40.0.0.0. ( if you are doing this practical after configuring pervious example don't forget to remove the last access list 101. With no access-list command. Or just close the packet tracer without saving and reopen it to be continue with this example.) R1(config)#access-list 102 deny ip host 10.0.0.3 40.0.0.0 0.255.255.255 R1(config)#access-list 102 permit ip any any R1(config)#interface fastEthernet 0/0 R1(config-if)#ip access-group 102 in R1(config-if)#exit R1(config)# Verify by doing ping from 10.0.0.3 to 40.0.0.3. and 40.0.0.2.It should be reqest time out. Also ping computers of other network. ping shuld be sucessfully. Once you have calculated the wild card mask rest is same as we did in pervious example R2>enable Enter configuration commands, one per line. End with CNTL/Z. R2(config)#access-list 2 deny 10.0.0.0 0.255.255.255 R2(config)#access-list 2 permit any R2(config)#interface fastethernet 0/1 R2(config-if)#ip access-group 2 out R2(config-if)# To test first do ping from 10.0.0.3 to 40.0.0.3 it should be request time out as this packet will filter by ACL. Then ping 30.0.0.3 it should be successfully replay. Network to Network Access List Task Students lab is configured on the network of 10.0.0.0. While management's system remain in the network of 40.0.0.0. You are asked to stop the lab system from gaining access in management systems Now we will block the network of 10.0.0.0 from gaining access on the network 40.0.0.0. ( if you are doing this practical after configuring pervious example don't forget to remove the last access list 101. With no access-list command. Or just close the packet tracer without saving and reopen it to be continue with this example.) R1(config)#access-list 103 deny ip 10.0.0.0 0.255.255.255 40.0.0.0 0.255.255.255 R1(config)#access-list 103 permit ip any any R1(config)#interface fastethernet 0/0 R1(config-if)#ip access-group 103 in R1(config-if)#exit R1(config)# Verify by doing ping from 10.0.0.3 and 10.0.0.2 to 40.0.0.3. and 40.0.0.2.It should be reqest time out. Also ping computers of other network. ping shuld be sucessfully. Network to host Task For the final scenario you will block all traffic to 40.0.0.3 from the Network of 10.0.0.0 To accomplish this write an extended access list. The access list should look something like the following. R1(config)#interface fastethernet 0/0 R1(config-if)#no ip access-group 103 in R1(config-if)#exit R1(config)#no access-list 103 deny ip 10.0.0.0 0.255.255.255 40.0.0.0 0.255.255.255 R1(config)#access-list 104 deny ip 10.0.0.0 0.255.255.255 40.0.0.3 0.0.0.0 R1(config)#access-list 104 permit ip any any R1(config)#interface fastethernet 0/0 R1(config-if)#ip access-group 104 in R1(config-if)#exit R1(config)# Verify by doing ping from 10.0.0.3 and 10.0.0.2 to 40.0.0.3.It should be reqest time out. Also ping computers of other network. ping shuld be sucessfully.