Right now, there is a route which I guess it was automatically defined while setting the L2TP-client, and does not show in these export configs… The guides I followed used an “intermediary” private network (i.e. 10.200.1.1). The route shows as active, but the remote subnet is still unreachable.
Dst. Address Gateway
10.200.1.1/32 VPN interface # route to reach L2TP server through VPN interface?
192.168.1.0/24 10.200.1.1 # route to reach remote subnet from assigned private IP to VPN connection?
192.168.1.0/24 VPN interface # Same as above?
is that from a security perspective or CPU performance impact on the router?
thanks
Well, from a personal/beginner perspective (still reading about it, advice welcome), we think that WireGuard VPN should be set up in each computer, right? Instead of a connection from router to router (site to site)? Which for us is undesired.