I’m trying to send multiples routes (10.0.0.0/8 network and 172.16.0.0/12 network) to my L2TP client (Windows 7), but I’m only getting the 10.0.0.0/8 network being installed in Windows routing table
On client side (Windows 7) the 10.0.0.0/8 network is being automagically installed in route table.
Default route is not being installed (great, my aim is to send only specific traffic inside the L2TP tunnel)
There is, but not on Mikrotik. The Windows embedded VPN client sends a DHCPINFORM message through the L3 tunnel, and expects a response carrying Option249, which is a routing table.
Mikrotik does support this mechanism for IKEv2, but not for L2TP. To use IKEv2 as a responder at Mikrotik and as a mode of the embedded VPN client on Windows, you currently have to use a machine certificate (not a user one) on the Windows.
You can configure “persistent” routes (using -p parameter when adding them) on Windows, with gateway address 0.0.0.0 and interface set to the VPN virtual one, which become active only when the interface is up.