While we might agree that there is some efficiency in applying the access list as inbound on the public interface instead of outbound on the private interface (catch the traffic and deny it sooner) you are creating essentially the same access list as mohammad did. If it did not work as outbound on the private interface I do not see what would make it work inbound on the public interface. Do you have a theory to explain that?
I believe that we need to investigate why the access list did not work for mohammad. If the x.x.x.x does correctly identify the server then it looks to me like his access list should have worked. Perhaps mohammad can supply a bit more detail about the topology of his network and the interface config where he attempted his access list. That might give us a better understanding of the issue.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...