1 / 23

Managing IP Traffic with ACLs

Managing IP Traffic with ACLs. Configuring IP ACLs. Outline. Overview Implementing ACLs Configuring Standard IP ACLs Configuring Extended IP ACLs Using Named ACLs Configuring vty ACLs Guidelines for Placing ACLs Verifying the ACL Configuration Summary. ACL Configuration Guidelines.

jana
Download Presentation

Managing IP Traffic with ACLs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Managing IP Traffic with ACLs Configuring IP ACLs

  2. Outline • Overview • Implementing ACLs • Configuring Standard IP ACLs • Configuring Extended IP ACLs • Using Named ACLs • Configuring vty ACLs • Guidelines for Placing ACLs • Verifying the ACL Configuration • Summary

  3. ACL Configuration Guidelines • ACL numbers indicate which protocol is filtered. • One ACL per interface, per protocol, per direction is allowed. • The order of ACL statements controls testing. • The most restrictive statements go at the top of the list. • The last ACL test is always an implicit deny any statement, so every list needs at least one permit statement. • ACLs must be created before applying them to interfaces. • ACLs filter traffic going through the router. ACLs do not filter traffic originating from the router.

  4. Standard IP lists (1-99) Extended IP lists (100-199) Standard IP lists (1300-1999) (expanded range) Extended IP lists (2000-2699) (expanded range) ACL Command Overview Step 1: Set parameters for this ACL test statement (which can be one of several statements). Router(config)# access-list access-list-number {permit | deny} {test conditions} Step 2: Enable an interface to use the specified ACL. Router(config-if)# {protocol} access-group access-list-number {in | out}

  5. Activates the list on an interface Sets inbound or outbound testing Default = outbound no ip access-group access-list-number removes ACL from the interface Standard IP ACL Configuration Router(config)# access-list access-list-number {permit | deny | remark} source [mask] • Sets parameters for this list entry • IP standard ACLs use 1 to 99 • Default wildcard mask = 0.0.0.0 • no access-list access-list-number removes entire ACL • remark lets you add a description for the ACL Router(config-if)# ip access-group access-list-number {in | out}

  6. Standard IP ACL Example 1 • Permit my network only.

  7. Standard IP ACL Example 2 • Deny a specific host.

  8. Standard IP ACL Example 3 • Deny a specific subnet.

  9. Extended IP ACL Configuration Router(config)# access-list access-list-number{permit | deny} protocol source source-wildcard [operator port] destination destination-wildcard [operator port] [established] [log] • Sets parameters for this list entry Router(config-if)# ip access-group access-list-number {in | out} • Activates the extended list on an interface

  10. Deny FTP from subnet 172.16.4.0 to subnet 172.16.3.0 out E0. Permit all other traffic. Extended ACL Example 1

  11. Deny only Telnet from subnet 172.16.4.0 out E0. Permit all other traffic. Extended ACL Example 2

  12. Using Named IP ACL Router(config)# ip access-list {standard | extended} name • Alphanumeric name string must be unique. Router(config {std- | ext-}nacl)# {permit | deny} {ip access list test conditions} {permit | deny} {ip access list test conditions} no {permit | deny} {ip access list test conditions} • Permit or deny statements have no prepended number. • “no” removes the specific test from the named ACL. Router(config-if)# ip access-group name {in | out} • Activates the named IP ACL on an interface.

  13. Filtering vty Access to a Router • Five virtual terminal lines (0 through 4) • Filter addresses that can access the router vty ports • Filter vty access originating from the router

  14. How to Control vty Access • Set up an IP address filter with a standard ACL statement. • Use line configuration mode to filter access with the access-class command. • Set identical restrictions on every vty.

  15. vty Commands Router(config)# line vty {vty# | vty-range} • Enters configuration mode for a vty or vty range Router(config-line)# access-class access-list-number {in | out} • Restricts incoming or outgoing vty connections for addresses in the ACL

  16. vty Access Example Controlling Inbound Access access-list 12 permit 192.168.1.0 0.0.0.255 (implicit deny any) ! line vty 0 4 access-class 12 in • Permits only hosts in network 192.168.1.0 0.0.0.255 to connect to the router vty

  17. ACL Configuration Guidelines • The order of ACL statements is crucial. • Recommended: Use a text editor on a PC to create the ACL statements, then cut and paste them into the router. • Top-down processing is important. • Place the more specific test statements first. • Statements cannot be rearranged or removed. • Use the no access-list number command to remove the entire ACL. • Exception: Named ACLs permit removal of individual statements. • Implicit deny any will be applied to all packets that do not match any ACL statement unless the ACL ends with an explicit permit any statement.

  18. Place extended ACLs close to the source. Place standard ACLs close to the destination. Where to Place IP ACLs

  19. Verifying ACLs wg_ro_a# show ip interfaces e0 Ethernet0 is up, line protocol is up Internet address is 10.1.1.11/24 Broadcast address is 255.255.255.255 Address determined by setup command MTU is 1500 bytes Helper address is not set Directed broadcast forwarding is disabled Outgoing access list is not set Inbound access list is 1 Proxy ARP is enabled Security level is default Split horizon is enabled ICMP redirects are always sent ICMP unreachables are always sent ICMP mask replies are never sent IP fast switching is enabled IP fast switching on the same interface is disabled IP Feature Fast switching turbo vector IP multicast fast switching is enabled IP multicast distributed fast switching is disabled <text ommitted>

  20. Monitoring ACL Statements • wg_ro_a# show {protocol} access-list {access-list number} • wg_ro_a# show access-lists {access-list number} • wg_ro_a# show access-lists • Standard IP access list 1 • permit 10.2.2.1 • permit 10.3.3.1 • permit 10.4.4.1 • permit 10.5.5.1 • Extended IP access list 101 • permit tcp host 10.22.22.1 any eq telnet • permit tcp host 10.33.33.1 any eq ftp • permit tcp host 10.44.44.1 any eq ftp-data

  21. Summary • Following the ACL configuration guidelines and commands is important to successfully implement ACLs. • To configure standard IP ACLs on a Cisco router, you must create a standard IP ACL and apply an ACL on an interface. • To configure extended IP ACLs on a Cisco router, you must create an extended IP access list range and apply an ACL on an interface. • The named ACL feature allows you to identify IP standard and extended ACLs with an alphanumeric string (name) instead of the current numeric (1 to 199 and 1300 to 2699) representations.

  22. Summary (Cont.) • For security purposes, you can deny Telnet access to or from a router’s vty ports. Restricting Telnet access is primarily a technique for increasing network security. • ACLs are used to control traffic by filtering and eliminating unwanted packets. Proper placement of an ACL statement can reduce unnecessary traffic. • The show command can be used to verify ACL configuration.

More Related