I have set up a ikev2 VPN server which is working flawlessly in Windows 8. When connecting to the same VPN server using Windows 10 (using the built-in ikev2 client), I'm experiencing some strange behaviors. It appears that Windows 10 is either 1) forcing split tunneling - but only for the virtual IP pool not the VPN server network - this is useless or 2) the routing is not being set up correctly to let the client know how to route VPN traffic to the VPN server. 

For example, I have a client that pulls 10.1.0.1 from the address pool 10.1.0.0/24.  The VPN gateway is on the subnet 172.16.0.0/24.  The VPN connects correctly, but when I try to access an IP in 172.16.0.0/24, the traffic is sent over the hardware NIC vs. over the VPN tunnel.  When trying to access an IP from 10.1.0.0/24, the traffic is properly routed over the VPN tunnel.

Connecting with Windows 8 and Windows Phone 8 do not exhibit the same problems... both connect and communicate with the network behind the VPN gateway without any issue.

Any idea what is going on