Comments
-
Hi Bruce, Everything is working now. I had to create an Alias for the nated IP and add it to the policie. Thanks for the help.
-
They told me that they dont see anything on their logs, that they see their traffic leave their Fortigate, but nothing comming in. I also oppened a support ticket with Watchguard to see if they can help. Do I have to create anything else other than the BOVPN and the two policies? Do you see everything correct on my end?…
-
My mistake... Edited the first post clarifying everything. Local server: 10.0.9.17/32 Remote server: 10.0.1.131/32 NAT Local server: 192.168.150.17 NAT Remote server: 192.168.250.131/32 Also, you can see the screenshots what the configuration is. Sorre for the confusion. Thanks!
-
Yes, they told me that they are doing a NAT on their end. I have two policies created as you can see on the pictures, one for outgoing, from my real IP address to the tunnel and one from the tunnel to my real IP address On the traffic monitor and can see the traffic being accepted 2022-01-27 22:18:08 Member1 Allow…
-
Hi, the tunnel is UP (both phases) but we cannot ping nor stablish any communication. I spent so much time looking at this and Im getting a bit stuck right now. I leave some screenshots of the configuration I made Configuration: REDACTED Can you see anything wrong on our end? On the other end theres a Fortigate I have no…
-
Thanks, I've followed the manual you posted and it seems fine.
-
On the destination part I had it locked on two public IPs, changing it to ANY did the work.
-
It worked as you described. Thank you very much :smile:
-
Ill try that, thanks!
-
Hi Bruce_Briggs, thanks for the response. I followed that, but on the step 7 only added the desired External interface, but it doesnt seems to work, is still going out through the default External interface. Any advice on what to check?