Hi  @Vincent-TP, thank you for your reply.

I have two L2TP VPN on the router, and I also configure two policy routing for them.

If I use one of them at the time, it works, but I can't use both of them at the same time.

The 2nd VPN connection activated, has no access to the internet.

It look like a route problem, as both vpn have the same "REMOTE LOCAL IP" address of 10.1.2.1 (and I can't change it)

(are these 'remote local ip' locally defined by the vpn controller/client, or we received them from the vpn server?)

In the Insights/Routing Table, when I activate only 1 VPN connection, I get these two additional routes:
 

ID 4,    Destination: 10.1.2.1,    NextHop: 0.0.0.0,    Interface l2tpUK

ID 14,    Destination: 0.0.0.0,    NextHop: 10.1.2.1,    Interface l2tpUK
 

and it's works as it should. (works with l2tpUK or l2tpUSA, as long as there only one connection enable at the time)

When I activate the 2nd VPN connection, there is no new route added for the 2nd VPN, and the 2nd VPN don't have

internet access.

I don't have much logs, I don't know how/where to enable a debug mode for that, but maybe there is and

error like "address 10.1.2.1 already in use" somewhere... ? :-)

I'm wondering if I could change the REMOTE LOCAL IP of the 2nd VPN connection, maybe there would be two new

routes added, something like

ID 5,    Destination: 10.1.3.1,    NextHop: 0.0.0.0,    Interface l2tpUSA

ID 15,    Destination: 0.0.0.0,    NextHop: 10.1.3.1,    Interface l2tpUSA

That's wrap up my limited understanding of the situation.

Hi  @Vincent-TP 

Vincent-TP wrote

How about the remote server of them? Did you use the the same domain name?

 

You can try with different remote subnets, such as changing one of them to 10.1.3.1/24.

I use a vpn provider (torguard) so I can't change the "remote server" address, I have to use the one from the provider.

For the subnets, yes, I try to change it to 10.1.3.1/24, and also to the "remote server /24 network address" from the vpn provider,

but in both cases, it's the same thing: the "remote local ip" is always 10.1.2.1

How can I change this 10.1.2.1 address ?

Maybe that's the reason why the routes for the 2nd vpn connection are never added to the routing table... ?

I'm not 100% sure, but I have the impression that this address (10.1.2.1) is "hard-coded" in the omada vpn client.

(If that's the case, then maybe it should be something we can be able to change in the UI.)
 

I will re-read the guides again, I don't know which step I missed.
Thank you Vincent.