Created on 11-28-2024 09:28 AM Edited on 11-28-2024 11:54 PM By Jean-Philippe_P
Description | This article describes how to originate traffic from the local FortiGate and reach resources behind the remote FortiGate in an IPsec site-to-site configuration. |
Scope | FortiOS 6.X and 7.X. |
Solution |
Assume the following topology:
192.168.10.0 ------- FortiGate1--------- IPsec --------- FortiGate2 -------- 192.168.1.X.
The proposed configuration will make it possible to produce a ping from a local FortiGate1 to the resource 192.168.1.X behind the remote FortiGate2 without using ping-options to select an interface.
First, it is necessary to assign an IP to the IPsec tunnel interface, for this, refer to: Configure IP address on an IPSec tunnel i... - Fortinet Community.
In this example, the assigned IP address to the tunnel interface will be 192.168.168.1:
After this, it will be necessary to create an Address Object with the IP assigned to the tunnel interface and add it to the phase2 selectors on both devices. From the FortiGate1 side, it would be added as a local phase2 selector, and in the FortiGate2, it will be added as a remote phase2 selector:
FortiGate1:
FortiGate2:
To conclude, it will be necessary to configure this address in the Firewall Policy for the incoming traffic from the tunnel in the FortiGate2:
This will make it possible to reach resources behind the remote FortiGate2 from the IPsec tunnel interface in the local FortiGate1:
Routing table for Test=0
diagnose ip address list |
Excellent Article @scampos ! Keep up the great job!
Thank you for your contribution @scampos
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 2024 Fortinet, Inc. All Rights Reserved.