How to configure IPsec VPN on FortiGate Firewall - Site-to-Site VPN Tunnel

[@ivanmoss4588]

Can you please create a video on how to set up a captive portal via Azure AD?

[@GetoM-b6w]

Hello, thank you for the video. I would like to ask, is there a way to ping the local LAN Gateway (in the video it is 192.168.1.1) without having to set the source IP before pinging? Thank you.

[@IgoroTech-Official]

hi, it depends on your network setup, if you only have one VLAN then no need for you to select the source, but if you have multiple VLAN's or multiple LAN subnet then you better specify the source specially if you did not allow all VLAN's to access to remote site. by default, its auto.

[@GetoM-b6w]

@@IgoroTech-Official Thank you. Yes, in each Site I have only 1 VLAN 172.16.0.0/16 and 172.17.0.0/16 But I can't ping to Local Gateway without selecting Source I need to select Source to ping to other Local Gateway I mean Ping from Fortigate to the other side's Local Gateway. By the way my topology is the same as in your video.

[@IgoroTech-Official]

@@GetoM-b6w as long as you can ping the remote local gateway once selecting the source then should be no issue. Since by default it's auto then it might be using your WAN, DMZ or other network gateway to reach the remote site.

[@GetoM-b6w]

@@IgoroTech-Official Thank you. Yes, both clients can ping each other and communicate with each other. But between Fortigate and other clients, they cannot ping. You have to select the Source IP first before you can ping. I want to know if there is a way to avoid setting the Source IP before pinging to the other side's Local Gateway. Thank you.

[@learnfirewall]

@IgoroTech-Official is it necessary to create reverse route ? without reverse VPN will not work !!

[@IgoroTech-Official]

hi there, yes, it's necessary to create a reverse route.