28.06.2014 Views

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

Learning by Doing: CISCO Certified Network ... - SCN Research

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Paper Lab: Access Control Lists<br />

Objective:<br />

To learn the fundamentals of writing standard, extended, and named Access Control List<br />

statements.<br />

Background:<br />

An access control lists (ACL) is a sequential collection of statements that control access<br />

to or from a network or subnet. The ACL statements are processed in the order in which<br />

they appear. There really is nothing magical about them…we just need to use them<br />

carefully and understand the logic of ACL’s. ACL’s consume large amounts of resources<br />

since every single packet coming and going is compared against every single ACL<br />

statement. In this respect we want to use them sparingly. Large amounts of ACL<br />

statements are best left to firewall and security devices…if you use lots of ACL<br />

statements you are actually turning your router into a firewall device. Creating and<br />

implementing ACL’s is a two step process:<br />

1. create the ACL<br />

2. apply the ACL to an interface<br />

You can write ACL’s for a variety of conditions and scenario’s. You will learn about 3<br />

of the basic ACL’s: Standard, Extended, and Named. Two of the other ACL’s you will<br />

learn about in CCNP school are Dynamic (a.k.a “Lock and Key”) and Reflexive. A<br />

standard ACL controls access using an IP address or range of addresses. An extended<br />

ACL controls access to specific ports for IP addresses. A named ACL uses a name<br />

instead of a number to do the same thing as standard or extended ACL’s<br />

We have some very simple rules to follow when creating ACL’s on your router.<br />

We have already discussed the first:<br />

1. ACL’s are sequentially processed<br />

2. ACL’s are compared until a match is made…if no match is made then the<br />

packets are dropped and not processed.<br />

3. There is an implicit “deny” statement at the end of every permit statement,<br />

BUT no implicit “permit” statement for every deny…watch out!<br />

4. Place standard ACL’s as close to the destination as possible. For now use<br />

“out” with standard ACL’s on the interface (more on this later).<br />

5. Place extended ACL’s as close to the source as possible. (The S’s do not<br />

go together) For now use “in” with extended ACL’s on the interface.<br />

Access Control Lists are also numbered. We have different numbers for our different<br />

purposes, protocols, and types of ACL’s. Let’s look at those numbers now:<br />

337

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!