FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
kmohan
Staff
Staff
Article Id 362218
Description

 

This article describes that in IPsec Site-to-Site VPN or DailUp VPN, there is one-way traffic and no return traffic from FortiGate to other FortiGate firewalls.

 

Scope

 

FortiGate.

 

Solution

 

Topology:

Local Server --------FortiGate-1-------IPSEC Tunnel-----FortiGate-2----Remote Server.


Configuration follows the below articles:

Technical Tip: How to configure VPN Site to Site between FortiGates (Using VPN Setup Wizard)

 

After the configuration is done, if the tunnels are up but the traffic is not sending out from FortiGate-1 to FortiGate-2.

 

Take Sniffer and debug:

 

dia sniffer packet any " host x.x.x.x and host y.y.y.y" 6 0 l 

 

x.x.x.x ---> Source IP address.

y.y.y.y ---> Destination IP address.

 

If the traffic is received from the server end but the traffic is sent out via 'Tunnel Interface', take the debug log with the below command line:

 

dia de reset

diagnose debug flow filter saddr x.x.x.x ------> Source IP address.

diagnose debug flow filter daddr y.y.y.y -------> Destination IP address.
diagnose debug flow show function-name enable

diagnose debug flow show iprope enable
diagnose debug console timestamp enable
diagnose debug flow trace start 999 ------> Number of captured packets.
diagnose debug enable

 

After 5 or 6 sec, disable the debug as follows:

 

diagnose debug disable

 

Debug errors usually get like 'denied by Forward Check policy or Policy ID 0'.

 

Check the firewall policy and configure with the below rules:

 

IPsec tunnel to Lan Policy -> Set Source and Destination to 'All'.

Lan Policy to IPsec Tunnel -> Set Source and Destination to 'All'.

 

Check it again, the two-way traffic sending out from the FortiGate-1 to the FortiGate-2.

 

Next Step:

It is necessary to check another Fortigate-2 with the same troubleshooting steps.
If the IP address is still not reachable, try to enable Source NAT from the 'Tunnel to Lan Policy'. After that, the IP address is reachable.

 

Then, it is not a FortiGate issue. Ask the user to check on the local subnet if the redirectional traffic is not allowed.

 

If the source IP addresses of the packets coming from the IPsec tunnel are not part of a network that the LAN devices know how to route back to, they might not respond correctly. By enabling SNAT, the source address is translated to an address on the LAN, ensuring the LAN devices see the traffic as originating from within their subnet.

 

Once the user allows the traffic from the local subnet, it will work fine.