Skip to main content
ppatel
Staff & Editor
Staff & Editor
Dec 30, 2021 9:33 AM UTC

Technical Tip: Enable path MTU discovery (PMTU)

  • Apr 16, 2026 12:17 PM UTC
  • 2 replies
  • 16724 views
  • Translate All
Description

This article describes how to enable path MTU (PMTU) discovery on Fortigate self-originated traffic.

Scope

FortiGate.

Solution
  • On 5.6 and 6.0 FortiOS lines, by default, any self-originated traffic from FortiGate (including proxy) has the DF bit set.

So fragmentation is not allowed along the path to the server which automatically triggered path MTU discovery when the intermediate router's MTU is smaller and thus FortiGate adjusted the packet size.

 

  • FortiOS v6.2 onwards, DF bit is not set for self-originated traffic. Path MTU discovery can be configured as below:

 

config system global
    set pmtu-discovery enable | disable (Disabled by default)

    set send-pmtu-icmp enable | disable (Enabled by default)
end

2 replies

Cristiano1
Explorer II
May 13, 2026 12:50 PM UTC
I encountered a very specific issue in version 7.4.11 on the Fortigat VM-Azure. In older firmware versions like 5.6, enabling PMTU globally makes sense... but it depends on the case... but since I'm having TCP retransmission problems where I'm losing packets, I even enabled MTU on the overlay interfaces and in the policy. I have a slight suspicion about the configured DHs, both auth and crypto AES256 with ikev2, but I don't see the bugs in v4.7.11 FG-VM... has anyone encountered a specific issue in this version?
Translate
Cristiano1
Explorer II
Jul 2, 2026 2:46 PM UTC
I updated to version 7.4.12, and the problem I was having was resolved.
Translate
Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024