Thanks for visiting! If you're new here, you may want to subscribe to my RSS feed. This blog posts regular tutorials, news, and study tips about networking, especially about Cisco CCIE related topics. Go ahead, subscribe to the rss feed! You can also receive updates from this blog via email. Thanks for visiting!
I read this over on group study, which i thought was a really good example of how of why in the CCIE lab we should try and deny the traffic you don’t want and permit the rest. You will probably run into a lot less trouble. This goes against the usual security advice of permit what you want and deny everything else. This is the Cisco CCIE lab, it’s not meant to be a collection of best practices (quite the contrary sometimes!)
Anyway, the problem was this: assume you are trying to prohibit DHCP within a given VLAN.
We could configure it with:
access-list 101 permit udp any eq bootpc any eq bootps
vlan access-map test1 10
action drop
match ip address 101
vlan access-map test1 20
action forward
vlan filter test1 vlan-list 11
This will work by first dropping what we don’t want and permitting everything else. But if we reverse the logic (ie permit IP traffic, then deny the bootp) with:
access-list 102 deny udp any eq bootpc any eq bootps
access-list 102 permit ip any any
vlan access-map test2 10
action forward
match ip address 102
vlan access-map test2 20
action drop
vlan filter test2 vlan-list 12
This will not work. Why? It seems logical. But what about ARP? Arp traffic will be matched by the second part of the vlan access-map (ethertype 0×806), so unless we have some static arp statements or they have been cached, we are in trouble.
Great example of vlan-access map logic.
Discussion
No comments for “VLAN Access Lists”
Post a comment