how to debug/troubleshoot one-way traffic IPSec tunnel
I am setting up a corporate IPSec network that consists of a UC520 at the head end (corporate office) and several Linksys WRV routers as remotes nodes/networks. I can see that ISAKMP and IPSec SA come up on both ends and I can ping the internal IP of the UC520 from remote networks. However I cannot ping any other private IP on the corporate network.
I see from "show cry ips sa" that packets are being decapsulated (remote to corporate) but none are encapsulated (corporate to remote). I also can see (from a traceroute) how packets from corporate to remote are sent out the UC520's default gateway to the Internet instead of being placed in the tunnel. This jives with what I see with "sho cry ips sa".
I made sure to create an ACL for NAT so that corporate to remote subnets are not NATed but other than that I don't know what else to check. I tried to do a "debug IP packet detail xxx" using an ACL to match corporate to remote traffic but the debug and ACL get no hits.
Re: how to debug/troubleshoot one-way traffic IPSec tunnel
You are absoultely correct. After doing more testing I realized the problem was only with private IPs (at the corporate site) that had a static NAT assigned to them. The IPs using PAT are working OK. I guess this is because the PAT IPs have an ACL that denys the NAT when its private to private traffic. The question now becomes how to do static NAT yet somehow use an ACL to deny private to private NAT like the PAT does.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :