Created on
‎12-06-2024
06:39 AM
Edited on
‎01-07-2026
10:52 PM
By
Jean-Philippe_P
| Description | This article describes how to block ICMP timestamps and replies for internal traffic that originates from behind the FortiGate. |
| Scope | FortiGate. |
| Solution |
This article demonstrates an example of how to block ICMP timestamps and replies for internal traffic that originates from behind the FortiGate.
The goal is to block ICMP timestamps and replies that originated from the machine behind port1 going to ANY internal interface.
config firewall service custom edit "TIMESTAMP" edit "TIMESTAMP_Replies"
Note: 'edit 0' will create a new policy using the next unused policy ID.
Results: Before the traffic is initiated, no traffic hits the policy.
After the traffic is initiated:
ICMP timestamp traffic is being denied.
Note: By default, normal ping through Windows does not send ICMP timestamp requests it.
To test the ICMP timestamp traffic, a tool such as hping3 or Nmap can be used to generate traffic. https://linux.die.net/man/8/hping3 ICMP timestamps can also be blocked using the 'local-in policy' if it is destined to the FortiGate interface.
Also, starting from FortiGate v7.6.0, the 'local-in policy' can now be configured in the GUI. Refer to this document for reference: Technical Tip: Creating a Local-In policy (IPv4 and IPv6) on GUI. |
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 2026 Fortinet, Inc. All Rights Reserved.