From the course: Cisco CCNA (200-301) Cert Prep: 3 Security, Automation, and Programmability

Unlock the full course today

Join today to access over 24,800 courses taught by industry experts.

Named ACLs

Named ACLs

From the course: Cisco CCNA (200-301) Cert Prep: 3 Security, Automation, and Programmability

Start my 1-month free trial Buy for my team

Named ACLs

“

- [Instructor] Named ACLs are my go-to, as their intended purpose is easy to understand based on how I name them. If it's for client filtering, I'll name it client filtering. If it's for OSPF filtering inbound, I'll call it OSPF filter inbound. While the logic and capabilities are the same as standard and extended ACL, configuration is done a bit differently. The quickest way to understand how they work is through a demonstration. I'll start with a standard named ACL, fig T, IP, access-list, standard. And now I'm going to name it filter-dmz-in. With named ACLs, all entries are done as sub commands, not as global commands like standard and extended ACLs. Now I'll add a couple of entries. Permit host, 100.65.0.1 and permit 100.66.0.0 0.0.0.255. Taking a look at how it's stored in the config, makes it a little clearer. Do show run, pipe begin, standard filter-dmz. I can see the ACL name, then the following sub commands. But, standard ACLs are boring, so let me do a demo on an extended…

Contents