Created on
11-03-2025
10:39 PM
Edited on
11-19-2025
09:24 PM
By
Jean-Philippe_P
| Description |
This article describes an issue where the DPD status of a tunnel may fail, causing the interface to be marked as inactive. |
| Scope |
FortiOS v7.4.4 and later, v7.6.0 and later. |
| Solution |
Symptoms:
Working scenario:
get router info routing-table database S *> 0.0.0.0/0 [10/0] via IPSec tunnel 10.0.0.1, [1/0] <----- Route is active.
diagnose vpn tunnel list name=IPSec ver=2 serial=1 10.56.6.245:4500->10.10.88.247:4500 nexthop=10.56.6.241 tun_id=10.0.0.1 tun_id6=::10.0.0.1 status=up dst_mtu=1500 weight=1
Non-working scenario: get router info routing-table database S > 0.0.0.0/0 [10/0] via IPSec tunnel 10.0.0.1 inactive, [1/0] <----- Route listed as inactive.
diagnose vpn tunnel list name=IPSec ver=2 serial=1 10.56.6.245:4500->10.10.88.246:4500 nexthop=10.56.6.241 tun_id=10.0.0.1 tun_id6=::10.0.0.1 status=up dst_mtu=1500 weight=1
The issue has multiple possible observed triggers, including changing tunnel configuration and HA failover events.
Workaround: Bringing the tunnel down and back up or rebooting the FortiGate temporarily restores VPN functionality, but the issue may reoccur. Disabling DPD in the tunnel configuration does not serve as a workaround.
Solution: This issue has been resolved in:
The fix optimizes the DPD status check and update process to prevent inactive route behavior.
Related articles: Technical Tip: Configuring DPD (dead peer detection) on IPsec VPN Technical Tip: Explanation of IPsec VPN DPD Options and On-Idle tunnel flushing process Technical Tip: Understanding and Troubleshooting IPSec VPN Disconnection Issues |
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.