09-14-2011 06:16 AM - edited 03-11-2019 02:24 PM
Hi,
I am reading the ASASM configuration guide.
About ACL, there is "Implicit Permits" that allows traffic from a higher secuity interface to a lower one. But on the other hand, "To allow any traffic to enter the ASASM, you must attach an inbound access rule to an interface; otherwise, the ASASM automatically drops all traffic that enters that interface."
This sounds confused. For example, if a context has only "inside" and "outside" interface, and I need permit all from "inside" and a filter for traffic from "outside". Then do I still need a "permit any" rule attach to the "inside" interface?
Thanks,
Solved! Go to Solution.
09-14-2011 06:21 AM
Hi,
Yes you are correct, the concept is different on ASA and ASASM.
On ASA, you dont need any ACL, if the traffic is going from inside to outside(higher to lower), beacuse there is an implicit allow acl.
On ASASM, you would definitely need an acl, if you are going from lower to higher security or from higher to lower security, ACL is very much needed.
Do let me know if you have any queries.
Thanks,
Varun
09-14-2011 06:21 AM
Hi,
Yes you are correct, the concept is different on ASA and ASASM.
On ASA, you dont need any ACL, if the traffic is going from inside to outside(higher to lower), beacuse there is an implicit allow acl.
On ASASM, you would definitely need an acl, if you are going from lower to higher security or from higher to lower security, ACL is very much needed.
Do let me know if you have any queries.
Thanks,
Varun
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide