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.
sprashant
Staff
Staff
Article Id 312318
Description This article describes the behavior when trying to ping the internet from any of the local interfaces of the FortiGate.
Scope FortiGate.
Solution

Trying to test connectivity via the command 'exec ping-options source <IP>' and then, trying to ping the internet will not work (exec ping 8.8.8.8). 

 

Ping from an interfacePing from an interface

 

Only echo request going, no responseOnly echo request going, no response

 

Debug flow:

 

flow debug.png 

Session output:

 

session output.png

 

By default, FortiGate can ping from only the interface from which the route is present in the FIB table. The reason is that the traffic generated from the firewall will be direct and no security policies will come into play. Hence there will be no NATting triggered and this is by design.

 

For example, trying to ping from a LAN port to the internet.

 

LAN port IP: 10.10.10.1

WAN port IP: X.X.X.X <- On the firewall.

Flow: Ping initiated from 10.10.10.1 <-----> ISP Gateway Router

 

Now, the ISP router will not recognize the internal IP, as it is expecting traffic from only X.X.X.X. Because of this, a drop will occur.