Windows 10: Windows IPsec Ikev2 client Rekeying default timeout

Hi!
Help me please!

Please tell me, is there a certain timeout for the connection of the IPsec client in Windows?
I have already set all the possible parameters on the server and everything has been tried, everything is turned off, the key exchange is turned off, the IPsec tunnel lifetime has been increased - but it's all useless - according to the server’s logs, it seems that Windows itself initiates the tunnel break after 7:45 + - hours

here, by reference, someone wrote that there is some kind of default timeout IKE_SA
http://rockhoppervpn.sourceforge.net/ref_tips_win7.html

a question for connoisseurs, is this really so? I can’t find this information anywhere
The versions of Windows 10 are different, from 1607 LTSB, 1903, - on all versions of IPsec ikev2 breaks the same way after about 7:45 hours ..

user authentication is carried out through the AD RADIUS server on Windows server 2008 not R2.
IPsec server - strongswan 5.8.2 at pfsense

:)

 

Prefix username in IPSEC Ikev2 connections

Hello,

I have windows phone 8.1. When I try to establish IPSEC Ikev2 connection with username and password, it prefixes username with the phone name.

For example:

If I enter "user" as username, Windows Phone change it to "Windows phone\user"

Any idea/setting how can I stop this behaviour ?

 

XBL client/server ipSec issuing CA (suspicious?)

When running antimalware/antilogger software it is now detecting 2 suspicious root CAs

XBL client IPsec issuing CA

XBL server IPsec issuing CA

why are they now showing up, should these be deleted or put in exclude safe list?

 

IKEv2 no longer working even after multiple fresh installs.

issue solved.

seems the issue is that Microsoft enabled automatic split tunneling for its corporate base. The only way to use IKEv2 is to set connection method to 'automatic'. Windows 10 then defaults to IKEv2 as its first connection type. You can verify this by looking
at 'Network Connections'. You will notice the connection is IKEv2. If IKEv2 does not work Windows 10 then tries SSTP next and then L2TP/IPsec and finally PPTP.

I like all my traffic sent though my VPN where as most corporate environments only need VPN for certain firewall issues, hence split tunneling by default makes more sense.

I will also acknowledge that I had been able to select IKEv2 in the past, I suppose a recent update changed this.

Microsoft, why haven't you made it clear to 'home' users that this is the situation?