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.
RADIUS and Symantec VIP.
I will use screenshots of ASDM, and at the end I will add the required CLI commands. the diagram below show a diagram of the steps the FW goes through when using 2FA authentication:
As you can see in Fig. 1&nbs...
Unable to get signature update from cisco.com
1. Make sure the router can get name resolution. Configure the router with a proper DNS name server.
ISR4451#utd threat-inspection signature update server cisco username xxxxx password yyyyy