Remote Access VPN traffic route

[cdfgallo]

ISSUE TYPE

• Bug Report

COMPONENT NAME

L2TP IPSec VPN on VPC VR

CLOUDSTACK VERSION

4.19.0

CONFIGURATION

Advanced networking, VPC

OS / ENVIRONMENT

SUMMARY

STEPS TO REPRODUCE

Enable remote access VPN on the source-NAT IP on VR on a VPC and configure a user.
Create a L2TP-IPsec connection on a client (I used the windows default client) and configure it not to receive default route from the remote VPN and disable class based route addition.
Connect to the remote VPN. 

EXPECTED RESULTS

As the connection goes up, the routes of the private networks of the VR are implemented in the routing table of the client

ACTUAL RESULTS

The routes to the internal networks of the VR are not passed on the VPN to the local client. As a workaround  I actually set a static permanent route in order to reach the remote side when enabling the VPN.

[weizhouapache]

@cdfgallo
AFAIK this is a known limitation of L2TP VPN
You can delete the default route and add some custom routes if needed