Forticlient IPSec VPN remains connected

[ATosI5]

Hello,

I am experiencing a strange issue with FortiClient VPN 7.4 and FortiGate 7.6

I've configured an IPSec Dialup server on specific public IP using certificates + xauth + no split tunnel (using aggressive mode).

Connection is fine and works as expected, but when I click on Disconnect (on client side), I got the disconnection on client but on fortigate connection is still shown as ACTIVE until dpd kill it. I checked on  client side using wireshark but cannot see any packet going out when clicking on disconnect.

Is this the right behavious or I missed something?

Thanks

[Shashwati]

hello

please refer to the document related to Dead Peer Detection (DPD) 

https://community.fortinet.com/t5/FortiGate/Technical-Tip-A-FortiGate-is-not-initiating-DPD-probes/t...

If there is incoming data traffic on ANY phase 2 selector from the IKE peer, FortiGate WILL NOT send DPD_R_U_THERE under any circumstance. 
 
If phase1 configuration has 'set dpd on-idle': FortiGate will send DPD_R_U_THERE if it does not receive any IPsec (data) traffic from the remote peer. If multiple IPsec (phase 2) selectors are configured but only one has incoming data traffic, no DPD will be sent. If no IPsec SA is available, FortiGate WILL send DPD. 
 
If phase1 configuration has 'set dpd on-demand': This is the default configuration. The behavior is like DPD 'idle', but with the additional requirement that FortiGate will only send the DPD_R_U_THERE if it has also sent data traffic over the IPsec tunnel during the previous DPD interval.
The device does not check whether the incoming traffic is related to the outgoing traffic. If there is incoming traffic on one phase2 selector and outgoing on another, FortiGate WILL NOT send DPD_R_U_THERE. If no phase2 selector is available, FortiGate WILL NOT send DPD. 

[ATosI5]

Hi Shashwati,

thanks for reply and for link about dpd.

My issue is not related to dpd but to the missing disconnect from client to fortigate.

Let me explain better:

1) I start connection from forticlient IPSec to Fortigate

2) Connection is esablished and I see it fortigate management.

3) THen I hit "disconnect" on client

4) After a couple of seconds client report Disconnected

If I then look at fortigate managemnet, I still see the connection as established. COnnection closes only after DPD (and fortigate report this).

I see this when I use a "full tunnel" vpn.

If VPN is a split-tunnel, then hitting disconnect on client causes both closure on client and fortigate.

I think that when establishing a full tunnel disconnect packets are sent WITHIN the tunnel (I see them with wireshark sniffing the virtual adapter).

I guess I did something wrong because I can't believe this is the default behaviour .

Thanks

[GriffinFlores]

Thank you so much for sharing link.

Spoiler

It’s funny how tech quirks like this can feel a bit like gambling—will the VPN reconnect or not? Speaking of gambling, I’ve been exploring platforms that offer free spins no deposit no Gamstop, which are a safe bet for entertainment. For anyone interested, this https://uk.notgamstop.com/bonuses/free-spins-no-deposit-no-gamstop/ page has some great info. Whether it’s fixing VPN issues or finding good deals, persistence always pays off!

[jaemskaellsora]

It's great to hear that the FortiClient IPSec VPN remains connected! A stable VPN connection is essential for maintaining productivity and secure access to resources. Fortinet’s reliability in this regard really stands out. If there are any tips or tweaks you've applied for optimization, sharing them could be helpful to others in the community to check more