![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhBP1CG9LTtxbzOAArjSRTVuB8b0yd_3VN33vbOXGr117I3mg6h_I_KqjlxQm2gSXAaL6qxLg2mnEFHYgqEnteYy2iTjm-haiJ5WFsOODz_DFQarvk89e2z4nwkOZqKSy_l2UNT0A/s400/VACLs.png)
In this blog post, we will obtain some good solid Tier 1 level knowledge regarding VLAN Access Control Lists or VACLs. These are often also referred to as VLAN Access Maps or just VLAN Maps; thanks to the syntax that is used in their creation.When you want to filter traffic that is moving from one VLAN to another, things are real CCNA-like and friendly We use an Access Control List. In fact, we should elaborate on that term a bit now in light of this discussion. We actually use a Router-based Access Control List or RACL.But what if we want to filter traffic that is flowing within a VLAN? On no, a Router-based Access Control List cannot help us! This is when we turn to the VLAN Access Control List. To help us understand this feature, let us create a topology and a sample scenario. Here is the simple topology:
For full information please visit to mention link:
No comments:
Post a Comment