ping response time spikes fortinet vpn tunnel

Nat (inside) 0 access-list inside_nat0_outbound Icmp unreachable rate-limit 1 burst-size 1

Same-security-traffic permit inter-interface Have the level of privilege at which you subsequently operate on this system.īanner motd You consent by entry into this system to the monitoring of your activities. I have been going through the 'Most common L2L and Remote Access VPN' troubleshooting doc form Cisco and will turn on NAT-T on both ends, but what else do I need to do?īanner motd If you are not authorised to access this system exit immediately.īanner motd Unauthorised access to this system is forbidden by company policies, national, andīanner motd Unauthorised users are subject to criminal and civil penalties as well as companyīanner motd By entry into this system you acknowledge that you are authorised to access it and I setup a different tunnel to my home ASA to ASA and everything works fine between the local ASA (192.168.150.1) and my home ASA (192.168.1.1).

If I try to ping from behind the local ASA and the tunnel isn't up, it never goes up. The catch is the VPN tunnel can only be initiated from the remote end (Fortigate VPN Firewall) and I can ping from a remote computer, see the ICMP packet enter the tunnel, and see in the log on the ASA the ICMP with the remote source IP and no echo reply is sent back over the tunnel.

I have established the VPN tunnel, verified with show isakmp and ipsec commands as well as watching the real time log in ASDM.

Ping response time spikes fortinet vpn tunnel