Arch Linux

Treyarch

Member

From: New Zealand

Registered: 2014-09-23

Posts: 48

Re: IPSec VPN To FortiGate wtih PSK and XAuth2 Not Routing Traffic?

UDP port 500 is used by ISAKMP, the IPsec key exchange protocol.

https://superuser.com/questions/245087/ … vpnc-error

So, I am just trying to get VPNC working, I put

IPSec gateway 
IPSec ID Any 
IPSec secret 
Xauth username
Xauth password 

When starting normally, I got the message about port being in use, so I changed it to some random port and still couldn't connect. Unless the IP needed to be the tunnel IP, I used the normal VPN one.

Treyarch

Member

From: New Zealand

Registered: 2014-09-23

Posts: 48

Re: IPSec VPN To FortiGate wtih PSK and XAuth2 Not Routing Traffic?

https://community.fortinet.com/t5/Forti … a-p/207149

I might ask my ISP to change this setting to "cisco" not FortiClient then see if that guide works, maybe the FortiClient being stupid does something extra

I tinkered around with xl2tpd again, it seems despite having a logfile param in the config it isn't creating a log, nor spitting out much more then "peer not authorized" when starting with -D interactively., though that was to the VPN assigned IP, not the public one.

xl2tpd[9642]: control_finish: Denied connection to unauthorized peer 172.31.0.1
xl2tpd[9642]: Connection 61887 closed to 172.31.0.1, port 1701 (No Authorization)
xl2tpd[9642]: control_finish: Connection closed to 172.31.0.1, port 1701 (No Authorization), Local: 61887, Remote: 15852

Oh I see from here; https://www.kerkeni.net/en/configure-l2 … os-5-2.htm
I should be using the public IP, however this times out on the default port and zenmap says no other ports are open (to scanning and the Forticlient doesn't require us to change any port let alone a facility to) so I don't think it's using l2tp

Last edited by Treyarch (2023-11-22 08:27:25)