• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 659
  • Last Modified:

Cisco Access Control List Order

With the code below, it allows a device to send a broadcast for a DHCP address. Once it gets a 192.168.81.x IP it should be able to communicate over the network.  My question is, doesn't the deny statements get hit first and 'match' the 192.168.81.x address before it hits the permit statement for that network?

ip access-list extended guest-wifi
 permit udp any any eq bootps
 permit udp any any eq bootpc
 deny   ip any 192.168.0.0 0.0.255.255
 deny   ip any 172.16.0.0 0.15.255.255
 deny   ip any 10.0.0.0 0.255.255.255
 permit ip 192.168.81.0 0.0.0.255 any
0
lconnell
Asked:
lconnell
1 Solution
 
Don JohnstonInstructorCommented:
My question is, doesn't the deny statements get hit first and 'match' the 192.168.81.x address before it hits the permit statement for that network?
You are correct. The "permit ip 192.168.81.0 0.0.0.255 any" should be before the deny statement.
0
 
AkinsdNetwork AdministratorCommented:
The 1st line of an acl is hit 1st before the 2nd line and so forth.
Once a match exists, the device stops checking through the lines.

In your example,  access-list extended guest-wifi
10  permit udp any any eq bootps
 20 permit udp any any eq bootpc
30  deny   ip any 192.168.0.0 0.0.255.255
 40 deny   ip any 172.16.0.0 0.15.255.255
50  deny   ip any 10.0.0.0 0.255.255.255
 60 permit ip 192.168.81.0 0.0.0.255 any

I added the sequence numbers to explain this
10 gets hit first, then 20, then 30 etc

60 would never get a hit as seq 30 matches that address. This means 192.168.81.0 /24 will be denied based on seq 30
0
 
gcl_hkCommented:
Better to clarify "match the 192.168.81.x address before it hits the permit" the matching address you mean source or destination?

This ACL should be working normally if it is for the guest network purpose. The deny statements are to prevent the 192.168.81.x subnet to communicate with any other internal subnets, and the last permit statement is to allow the 192.168.81.x to reach internet. No conflict at all.
0
 
Don JohnstonInstructorCommented:
Good catch gcl_hk.  I missed the source/destination (I'll blame it on the iPad)  :-)

You're absolutely right. Only traffic to private addresses would be blocked by the ACL.   Internet traffic would be permitted.
0
 
lconnellAuthor Commented:
Thank you to everyone who commented, very much appreciated! :)
0

Featured Post

Turn Raw Data into a Real Career

There’s a growing demand for qualified analysts who can make sense of Big Data. With an MS in Data Analytics, you can become the data mining, management, mapping, and munging expert that today’s leading corporations desperately need.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now