Created on
04-19-2005
12:00 AM
Edited on
03-06-2025
10:43 PM
By
Jean-Philippe_P
Description |
The article describes that FortiGate does not answer ping requests. |
Scope |
FortiGate v5.6.x and below. |
Solution |
Issue: PING is enabled as Administrative Access on the interface, yet the interface does not reply to Ping requests. Cause:Local-in policy or trusted hosts are defined for Admin accounts. Solution:
Trusted hosts also apply to ICMP echo requests. To have the FortiGate respond to ping requests whatever the originator, add a restrictive Admin account with no trusted hosts associated with it. For example, default 0.0.0.0/0.0.0.0. Give the new Admin account a complex name, set it with an Access Profile that has no privileges, and use a complex password.
Verify whether a local-in policy has been configured to block ping requests.
config firewall local-in-policy show
To verify the ping traffic, run the below command.
diag sniffer packet any " host x.x.x.x and icmp" 4 0 l
Note: From v6.0.x onwards, ping service on management interfaces are not included within the scope of trusted hosts. This means that it will be possible to ping the interface from an IP that is not included within trusted hosts.
Make sure Ping is enabled on the network interface:
config system interface edit portx -> Port number. set allowaccess ping end |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.