Hi all, I am able to connect to a Fortinet VPN server from Windows 10
using Fortinet Client v6.0.9.0277. My configuration is displayed in the
following 2 pictures: But, from linux mint, using strongswan I am unable
to connect. Here is my configuratio...
@AEK, thank you so much!Setting, as you
suggestedrightsubnet=172.28.2.0/24proved to be the working solution! Now
I can ping and access internal websites, also using dns names!When I
check the route as you suggested it looks like in your
example:user@...
This is strange as on Fortinet client from Win10 I am not setting any
subnet anywhere, the client does everything. By looking at the virtual
adapter it creates, I can see there:IPv4 Address. . . . . . . . . . . :
192.168.166.4(Preferred) Subnet Mask ...
@AEK, I don't have access on the remote FortiGate, but with the same
credentials and using the FortiClient from Windows 10 it is properly
working.One difference between the 2 OS that I noticed is that in
Windows 10 a new virtual adapter is created, w...
@AEK, yes 172.28.2.111 is the DNS server, I checked on the Windows 10
machine. user@Machine:~$ sudo ufw status Status: inactive
user@Machine:~$ dig something.internal.company.com @172.28.2.111 ;;
communications error to 172.28.2.111#53: timed out ;; ...
Update: it seems that I was not having the resolveconf package on my
linux system. After installing it, I no longer have those warnings
related to DNS in my connection log: user@Machine:~$ sudo ipsec up
FortinetVPN initiating Aggressive Mode IKE_SA F...
