01-21-2020 12:33 PM - edited 02-21-2020 09:50 AM
Hi Everyone,
I have scoured the web and have nearly mirrored the setup as outlined here:
https://community.cisco.com/t5/firepower/firepower-publish-internal-webserver/td-p/3672845
While following the guidelines for CISCO NAT rules.
NAT works as expected except I am hung up on the ACL Rules, and I have been now for the last week.
Here is what I have created:
I turned the default access rule to allow and then created the last rule to Block all traffic.
If I turn off the "Block all Traffic" Then NAT works as expected and everyone from the outside world can access my internal webserver. by the IP specified.
What do I need to do with my ACL list to allow my "WebserverPublic" to correctly work?
Solved! Go to Solution.
01-22-2020 07:26 AM
01-21-2020 12:38 PM
01-22-2020 07:21 AM - edited 01-22-2020 07:22 AM
Thank you for the advice RJI,
I did as you suggested and edited the rule as shown.
The trace comes back as follows.
However, unless I switch the default access control to allow, this does not work.
01-22-2020 07:26 AM
02-13-2020 12:31 PM
I had this working until I added an IPSEC tunnel.
Now Outbound binding an IP address to the server works but inbound External IP to the inbound server fails.
Show nat has this:
02-13-2020 12:49 PM
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