ACLs, Route Maps, Prefix Lists Flashcards
Where are common places where you would see an ACL being used?
QoS
NAT statements
Class-Maps
Route-Maps
VLANs
Switchports
What is one caveat that should be noted regarding outbound ACLs applied to a Router’s interface?
Traffic generated by the router will not be caught by the ACL (deny)
What are the valid numbers for standard ACLs?
1-99 and 1300 - 1999
What is the restriction of using standard ACLs?
Only the source IP address information can be filtered
What is the basic syntax for a standard numbered ACL?
R1(config)# access-list {number} {permit | deny} {ip-address} {wildcard-mask} [log]
AND/OR
R1(config)# access-list {number} {permit | deny} host
AND/OR
R1(config)# access-list {number} {permit | deny} any
What is the basic syntax for a standard named ACL?
R1(config)# ip access-list standard NAME
R1(config-std-nacl)# [seq-num] {permit | deny} {ip-address | any | host} [wildcard] [log]
Example:
R1(config)# ip access-list standard ACL_1
R1(config-std-nacl)# 30 permit 10.55.44.0 0.0.0.255 log
What is the command to apply a standard access-list to an interface?
R1(config-if)# ip access-group {number} {in | out}
What is the advantage of using a named standard ACL over a numbered ACL?
Flexibility to edit later by using sequence numbers
What are the advantages of using extended ACLs over standard ACLS?
- filter on source and/or destination IP address
- filter on source and/or destination port/protocol
What the numbers available to use for extended numbered ACLs?
100 - 199 and 2000 - 2699
What is the basic syntax to create a named extended ACL?
R1(config)# ip access-list extended NAME
R1(config-ext-nacl)# [seq] {permit | deny} {ip | udp | tcp} {src-address} {src-wildcard} {dest-address} {dest-wildcard} [eq {port-number}] [log]
Example:
R1(config)# ip access-list extended ACL_101
R1(config-ext-nacl)# 90 permit tcp 10.99.0.0 0.0.255.254 200.11.22.0 0.0.0.255 eq 443 log
What is the most common use of a Prefix List?
Match network ranges for the purpose of route filtering
What is the command structure for a Prefix List?
R1(config)# ip prefix-list [seq {number}] {network-prefix}/{mask-bits} {le | ge} {prefix-length} [{ge | le} {prefix-length}
Example: R1(config)# ip prefix-list 10.2.1.0/24 le 24
NOTE: the network-prefix is commonly called the high-order bit pattern and the mask is usually called the high-order bit-count.
What is the key reason to use a Prefix List over an Access List?
The ability to match multiple network ranges with a single statement (by way of the “le” and “ge” function).
What are the rules that dictate how Prefix Lists function?
- if not defined, sequence numbers begin with 5 and increment by 5
- Processing stops after the first top-down entry is matched
- implicit “deny all” at the end of the Prefix List