It's expected it's a new feature but what I would do in this case since hub-spoke, is to use IPSEC. It works and works good for site-2-site vpns. I do not consider the vpn-ssl. site-2-site in the traditional sense, you are a vpn-client no different than a forticlient from that perspective.
Also when it's down, did you do any debug ?
I would start 1st by taking your source-interface and throw that in a sniffer
e.g
diag packet sniffer wan1 "host x.x.x.x"
Since you have so much at play AWS, EIP, new-feature,etc.... I would open a support case.
Ken Felix
PCNSE
NSE
StrongSwan
SSL VPN as a client is described this way in documentation, so it is not correct to call it "site2site" but client-to-site. And in such case it is normal and expected for Fortigate to hide internal LAN , being the client.
So, if you are doing it in production - abandon this ssl-client thing (at least until FortiOS 7.0.4) and use regular IPSec that works perfectly well with AWS. If, on the other hand, you are playing with it for the adventure of it and to be a pioneer - great, when you find the answers be sure to update us, we'll be thankful :).
Agreed and if you want ipsec-client dialup. The fortigate has always supported this.
http://socpuppet.blogspot.com/2019/10/fortigate-dialup-vpn-ipsec-from-2nd.html
The sslvpn does the same, but with SSL ;) Neither arr true lan-2-lan fwiw.
Ken Felix
PCNSE
NSE
StrongSwan
So is GRE or L2TP being blocked? Just curious
Ken Felix
PCNSE
NSE
StrongSwan
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1740 | |
1108 | |
752 | |
447 | |
240 |
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.