05-15-2017 11:19 AM - edited 03-12-2019 02:22 AM
I have a client with ASA multicontext firewall running with Firepower 6.1 in it. They have limited bandwidth for Firepower on it with multiple 10 gig lines so they are restricting which traffic gets redirected to Sourcefire Module for fiiltering. They are trying to keep those ACLs as simple as possible, and are seeing results they arent totally happy with. Question is:
If you redirect specific traffic to the sourcefire based on an ACL associated with a service-policy per-interface, do those ACLs need to be bidirectional? What they are seeing for example is Inside-DMZ not getting redirected but the return traffic from DMZ-Inside on the same TCP session is getting redirected. Is that redirection bidirectional per-interface? Do they need an ACL that would say
permit Inside to Servers
permit Servers to Inside
on the same ACL if that policy was a class-map SFR for service-policy on the interface Inside?
Right now they just have "inside to Servers" and are still seeing redirects from "Servers to Inside", reportedly on same interface. I know its easy to test but wanted to ask the forum if that is the correct config method to use bidirection ACL on a specific interface policy for redirection to SFR module?
Thanks!
Solved! Go to Solution.
05-16-2017 07:19 AM
You will need to define both directions in the ACL. Even though the ASA is stateful, the traffic that gets sent to SFR is not.
HTH
05-16-2017 07:19 AM
You will need to define both directions in the ACL. Even though the ASA is stateful, the traffic that gets sent to SFR is not.
HTH
05-16-2017 07:58 AM
Thanks for verfying. Just wanted to be certain.
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