19.07.2013 Views

CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home

CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home

CCNA Complete Guide 2nd Edition.pdf - Cisco Learning Home

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.

Chapter 20<br />

IP Access Control Lists Lab<br />

- Remember that access lists use excessive router processing resources. Hence always implement<br />

access lists as short as possible, as effective as possible, and as efficient as possible.<br />

Standard IP Access Lists Configuration<br />

1<br />

172.16.1.2<br />

Access denied<br />

to ServerA<br />

2<br />

172.16.2.2<br />

3 4<br />

Fa1/0<br />

Fa1/0<br />

172.16.2.3 172.16.2.4<br />

Figure 20-1: Network Setup for Access Control List<br />

- Standard IP ACLs filter packets by examining only the source IP address in a packet. Standard<br />

ACLs are created with the access-list number 1-99 or 1300-1999 (expanded range), inclusively.<br />

There is no difference between a number to another.<br />

- IP ACLs configuration commands:<br />

Command Description<br />

access-list {access-list-num} {deny | permit} Global configuration command used to<br />

[host] {source-addr} [source-wildcard]<br />

add an entry into a standard access list.<br />

access-list {access-list-num} remark {text} Global configuration command used to<br />

add a comment for an access list.<br />

ip access-group {access-list-num} {in | out} Interface subcommand used to apply an<br />

access list on an interface.<br />

access-class {access-list-num} {in | out} Line subcommand used to apply an<br />

access list on VTY remote access lines.<br />

no access-list {access-list-num} Global configuration command used to<br />

remove an access list entirely.<br />

- TO-DO: Implement standard ACLs to deny the access of PC2 to ServerA.<br />

- Standard ACLs should be placed as near to the destination as possible, as standard ACLs often<br />

discard packets that are allowed to forward (or pass) when they are placed close to the source.<br />

Ex: If an inbound ACL is placed on RT2’s Fa1/0, PC2 will never go further than RT2! Hence the<br />

best place to deploy the ACL is on RT3’s Fa1/0 with an outbound standard ACL.<br />

- Another reason is security loopholes might exist when a link between routers fails – packets that<br />

pass through another new path might no longer be passing through the ACL-secured interface.<br />

139<br />

RT1<br />

S0/0<br />

RT2<br />

S0/0<br />

S0/1<br />

S0/0<br />

S0/1<br />

RT3<br />

S0/1<br />

Fa1/0<br />

ServerA<br />

172.16.3.2<br />

Copyright © 2008 Yap Chin Hoong<br />

yapchinhoong@hotmail.com

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

Saved successfully!

Ooh no, something went wrong!