192.168.11.1/24 - - > Windows computers
192.168.11.11/24 - - > Linux box
192.168.11.111/24 - - > Apple computer
By the way, the switch has not a IP address assigned, because it is not required. The Windows computer has Windows Firewall disabled, and the service of File and Printer Sharing (SMB) enabled. The Linux box is publishing three folders by running python -m SimpleHTTPServer TCP-PORT. The web publishing service is assigning an unique TCP port to each folder, from 10001 to 10003. The OS-X computer manages the switch through a serial port, sends some pings to Windows (192.168.11.1) and the Linux box (192.168.11.11), displays the content of each web folder (Text01, Text02...) and connects to the Windows computer through SMB. Everything happens as expected, everything is normal, nothing fancy. The interesting thing starts once the VACL commands are introduced to the switch. As you can noticed in the video below, the Windows computer continues working normally. That is to say, Windows continues answering PING and sharing folders. The lab has been focused on the Linux box. So, after introducing the VACLs commands in the switch, the Linux box stopped answering PING, also the administrator has decided to disable the TCP port 10003 to be reachable by the hosts in the same VLAN. Let's watch a video to get a visual idea, step by step of the described topology.
192.168.100.11/24 and 192.168.200.11/24 - - > Apple computer
192.168.100.12/24 and 192.168.200.12/24 - - > Linux box As the coming video shows, each computer can PING request and reply without any problem. But, as soon the VACL commands are deployed in the Switch, the normal development changes, and the addresses corresponding to the network 192.168.200.0/24 are sudenly stopped.