Windows 10: User VPN VWAN and IKEv2 - VPN stays connected in Windows but drops traffic until reconnect.

Hi,Is anyone else suffering with an IKEv2 AOVPN deployment with User VPNs or P2S VPNs in Windows 10/11?I have had 2 clients report the same issues with different Azure based networking topology's whereby the IKEv2 session stays connected for an hour but once the time has elapsed, the connection is still connected in Windows but the session is tunnel is disconnected. The only way to fix it is to reconnect.I've only been able to get it working on a Windows 11 vanilla build with an Insider Build Pack installed.

:)

 

A problem of Windows 10 VPN (Ikev2) connection

I tried to use ikev2 VPN on my windows 10 laptop, and connected successfully (at least it showed "connected"). However, when I checked my IP on google, it suggested that it didn't connect me to the VPN server at all. And other methods also proved that my
laptop didn't get access to the Internet via ikev2 VPN.

So are there anyone who also meet the same problem? Is it a bug on windows 10, or just something I do is wrong?

 

A problem of Windows 10 VPN (Ikev2) connection

I agree that something changed in Windows 10 here... I've been looking into this and it appears that Windows 10 isn't configuring the routing correctly or forcing split tunneling (but only using the client IP range as the source for the split tunneling).
For example, if I connect to my ikev2 vpn server, all my traffic is routed over my NIC, except when I try to use an IP in the virtual IP range of the client. And since only the virtual IP range gets routed over to the VPN server, the VPN is pretty much useless.

Has anyone heard of functionality changes in the ikev2 VPN implementation?

 

A problem of Windows 10 VPN (Ikev2) connection

I know this thread is old, but hopefully some info here can help those us bewildered by this new behavior in Windows 10 (desktop and mobile).

I replied with details in this thread
http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/why-doesnt-the-vpn-work-on-windows-10-mobile/607d23f9-eff0-44f6-9308-bbd250569966, but here are the basics:

• This is a feature called Split Tunneling, and will send traffic through a VPN only when it is inaccessible to the underlying connection (wired, WiFi, LTE, etc).
• The way to get around it is to avoid selecting any specific protocol for your VPN connection. Instead, choose Automatic.
• Along with that, you must choose Automatic when the connection is first setup. Changing and saving it to any other option will re-enable split tunneling and the only option to return force all traffic through the VPN is to create a new VPN connection with
  Automatic.
• With Automatic, the protocols are tried in this order until a connection is made: IKEv2, SSTP, L2TP, and PPTP. Been this was since Windows 7 as those are most to least secure protocols.

Again, more details are in my reply in the link above. Hope this helps.