11-30-2015 08:09 AM - edited 03-11-2019 11:58 PM
Morning. Engineers
I hope you can help me to figure out why is not working using ACL.
Model: ASA 5555-X
Version: 9.2(2)4
Multiple Context: Yes
Network1 10.100.0.0/24 (DMZ1 on physical subinterface) security-level 50
Network2 10.100.1.0/24 (DMZ2 on portchannel subinterface) security-level 50
Network3 10.100.2.0/30 (Routing to my LAN) security-level 50
LAN 192.168.200.0/24
I need Network2 only communicates with 192.168.200.0/24 through 10.100.2.0/30 with ACL's.
Using the command "same-security-traffic permit inter-interface" there is no problem it works but no security, because Network1 can communicate with Network2/3 and my LAN.
I was trying ACL in but no success.
access-list ROUTING extended permit ip 10.100.1.0 255.255.255.0 192.168.200.0 255.255.255.0
access-group ROUTING in interface Network3
packet-tracer input Network2 tcp 10.100.1.10 16789 192.168.200.10 80 detailed
It says communications was dropped because of ACL (I think global is deny any any).
Thanks for your time.
Solved! Go to Solution.
11-30-2015 09:59 AM
Hi,
yes, You need 'same security' command to allow the communication between same security-level interface. It is mendatory. However you could restrict commnunication between subnet on these interfaces with the help of Access-list.
Hope it answers your query.
Regards,
Akshay Rastogi
Remember to rate helpful posts.
11-30-2015 08:55 AM
Hi,
You would require this command to permit the traffic between interface of same security level.
But along with this command you can create ACLs to control traffic based on your security requirements.
Thanks,
Rishabh Seth
PS: Rate if it helps and mark answer as correct if it resolves your issue.
11-30-2015 09:00 AM
Hi, Rishabh
You mean that I need to use both that command (same-security-traffic permit inter-interface) and ACL?
Is there any way only to use ACL to communicate those networks?
Regards
11-30-2015 09:59 AM
Hi,
yes, You need 'same security' command to allow the communication between same security-level interface. It is mendatory. However you could restrict commnunication between subnet on these interfaces with the help of Access-list.
Hope it answers your query.
Regards,
Akshay Rastogi
Remember to rate helpful posts.
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