I've noticed that I can't ping a public device (on my block) from the vpn. The vpn is NOT my firewall, but another ASA (5520). The inside interface on the ASA is on my private side. From a host on the lan and not on vpn, I can ping this device. The path the packet would take is from:
In my experience, issues like this usually tie back to a routing problem. I've had similar issues where the echo request reaches the target but it is the reply that cannot find its way back to the VPN client.
I would suggest first getting packet captures throughout the topology and find what is being dropped (request or reply) and where it is being dropped. Once you know this, you can look for log or debug messages that explain why the packet is dropped and troubleshoot from there.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...