On the outward path traffic is directed through the VPN and straight in to the remote sites subent, however on the return path the traffic first hits the firewall before being re-routed back in to the subnet to the firewall (this was to avoid route statements on servers).
The problem with this is that the ASA denys TCP traffic on the return path as it did not see the original connection??
Deny TCP (no connection) Flags SYN ACK interface Inside
How do I either turn off this type of stateful inspection (not a great idea I know) or work around this?
How about using the "Nailed" option under the static configuration.
(Optional) Allows TCP sessions for asymmetrically routed traffic. This option allows inbound traffic to traverse the security appliance without a corresponding outbound connection to establish the state. This command is used in conjunction with the failover timeout command. The failover timeout command specifies the amount of time after a system boots or becomes active that the nailed sessions are accepted. If not configured, the connections cannot be reestablished.
Note Adding the nailed option to the static command causes TCP state tracking and sequence checking to be skipped for the connection. Using the asr-group command to configure asymmetric routing support is more secure than using the static command with the nailed option and is the recommended method for configuring asymmetric routing support.
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...