Skip to main content
ssteo
Staff
Staff
Sep 1, 2021 5:43 AM UTC

Technical Tip: FortiGate source-ping using SD-WAN rules

  • Sep 8, 2026 6:48 AM UTC
  • 0 replies
  • 9749 views
  • Translate All

Description


This article describes FortiGate source-ping using SD-WAN rules.


Scope

FortiGate.


Solution


FortiGate has 2 WAN links, which are PORT1 and PORT2.
One IPsec tunnel is tested.

kb_20629_1.png


There is one SD-WAN rule and no performance SLA.

 

kb_20629_2.png

 

 There is one default route.

 

kb_20629_3.png


FortiGate LAN is PORT3, which is 10.225.1.220/22.

 

kb_20629_4.png

 

The source IP 10.225.1.220 has been configured to ping 10.226.1.254 but fails. 10.226.1.254 is a PC on the IPsec LAN.

 

kb_20629_5.png


kb_20629_6.png


Ping from LAN PC and able to ping because it will use SD-WAN rules.

 

kb_20629_7.png

 

kb_20629_8.png

 

Found that in FortiGate CLI, to let the interface IP 10.225.1.220 ping the opposite 10.226.1.254, under 'ping-option', 'use-sdwan' needs to be configured as 'yes'.

 

Then FortiGate is able to ping 10.226.1.254. So it is not related to performance SLA, just the ping option on FortiGate only.

 

kb_20629_9.png


Note: By default, execute ping generates locally originated traffic from the FortiGate itself. Unlike forwarded traffic from client devices, locally originated traffic does not automatically follow SD-WAN rules for ping testing.


Enabling execute ping-options use-sdwan yes instructs the FortiGate to evaluate the existing SD-WAN rules when selecting the egress interface for the ping. This behavior affects the diagnostic ping operation and helps verify how traffic would be forwarded through the configured SD-WAN policy.

    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