We had implemented a Cisco ASA replacing a Sidewinder FW on our network. The Network has an ironport proxy even before which does HTTP connect (converting port 1-6553 to port 80). When we migrated from Sidewinder to ASA we made all the flow and policies and even natting the same.
The problem is, there are websites that the user cannot access. Seems like it is blocked by the firewall. Those websites where working before on Sidewinder FW but have problems when migrated to ASA. All is fine when we bypass the FW by connecting to F5 load balancer port. So ASA is the problem as isolated. All tcp, ip, and UDP traffic from Proxy are allowed to pass on the ASA but still encountering the problem. I am looking at the inspection policies or other policies that ASA has. Hope someone can help me turn off those inspection policies or whatever is making the ASA filtering so intensive.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...