Hi All,
I purchased a Fortigate 30D for home use. It is connected on the LAN to my BT home hub5 using an internal IP address.
I can connect a PC to the Fortigate LAN and set up a NAT to internet traffic just fine.
I decisded to try and build a VPN connection to AWS. The tunnel is built at both ends and shows as up. However when I try to connect to a device in AWS, it fails. A debug seems to show that traffic hits the VPN tunnel correctly, then it looks like it loops because I see a second traffic flow coming from the Ipsec tunnel? I suspect its an issue with haveing a NAT then another NAT on the HomeHub.
Has anyone been able to set up a similiar scenario?
Thanks
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Dear Friend,
Have you created a policy for the tunnel? If yes, make sure you have a NAT enable.
From the word "Loop" , it sounds like a gateway configuration, make sure it.
Also, make sure of the IP address you defined, it's not conflicting somewhere.
Since there is no clear problem, I am just giving you a general assumption.
Regards,
Shehab
Hi Shehab,
Thanks for the reply. I got it working, turns out there was a missing route on the AWS side!
All good now!
Thanks
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 |
---|---|
1705 | |
1093 | |
752 | |
446 | |
230 |
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.