@helviojr said in IKEv2 VPN for Windows 10 and OSX - HOW-TO!:
@josey:
I guess i have to add default route for servers subnet? but what is my gw then, because there is no IPV4 address of IKEv2 under connection details.
I didn't test IKEv2 yet (still on L2TP with IKEv1), but it seem you can create route using device, instead of gateway IP:
use ipconfig to get the name of each device (you probably can get those form GUI also);
use route print to get the number of each interface, and get the one of your VPN device (the table at the begining of "route print" command output);
create the route using "IF" option instead of the gateway address:
route ADD 10.10.10.0 MASK 255.255.255.0 IF 10 -p
(this would create a route to subnet 10.10.10.0/24 through interface number 10)
Sometimes I prefer the Powershell command:
Add-VpnConnectionRoute -ConnectionName "[vpn_connection_name]" -DestinationPrefix [network]/[Prefix]
so for example it becomes:
Add-VpnConnectionRoute -ConnectionName "[vpn_connection_name]" -DestinationPrefix 10.10.10.0/24
I use this because connection name is simple to recognize even for people with no technical skills.