ASA acting as a VPN server for incomgin client connections. The ASA outside interface has a 192.168.8.X address. Infront of the ASA is a internet connected firewall that has a one to one NAT mapping from a public routable IP to the ASA's outside interface. I have no visibility into the firewall doing the NAT but they tell me they have the relevent IPsec ports allowed.
The client fails to connect and I see virtually no traffic on the ASA for the connection attempt. Assuming the right ports are allowed NAT is the most likely cause for this failure? Can someone give some detail on how NAT would be breaking it.
Make sure the allow UDP 4500 In addition to just UDP 500 and IP protocol 50. When either end is behind a NAT device (client or headend) UDP 4500 starts getting used once both ends realize one of them is behind NAT.
Other than that, make sure that you have 'crypto isakmp nat-traversal' enabled. You show see it in the config if you do a 'show run all crypto isakmp nat-traversal'.
So are you saying that I can connect a client VPN to an ASA with a non public IP provided another device infront of it e.g. a Juniper\Checkpoint firewall etc is doing one to one NAT for that ASA to a public IP?
I thought you couldnt do that or is the UDP 4500 the NAT traversal thats taking care of this?
This month, we're excited to bring awareness to a newly formed partnership between Cisco Secure and IBM.
Securing today's dynamic enterprise applications is critical. With hybrid and multi-cloud adoption, traditional network-based security ran into limita...
Listen: https://smarturl.it/CCRS8E42Follow us: twitter.com/CiscoChampion
APIClarity is an open source, cloud-native visibility tool for APIs. It utilizes a Service Mesh framework to capture and analyze API traffic and identify potential risks.
Hello everyone, A new video in the Cisco Secure Terraform Series has just been published. If you are interested in Infrastructure as Code, and Terraform, you don't want to miss out on this amazing series with Jason "Canadian Bacon" Maynard! Newe...
The Cisco Secure Firewall and SecureX teams are looking for feedback from active Secure Firewall users who may or may not have already activated SecureX. Your responses will help us improve the Firepower experience in SecureX. Th...