NetworkManager vpn con fails when no gateway

When I try to activate an OpenVPN connection using the network manager command:

nmcli connection up vpn_conn 

I get the following error:

Error: Connection activation failed: Could not find source connection. 

I only get the error when there is no gateway set on the ethernet connection. Does anyone know why?

I added unicast static routes to the vpn server. What is more interesting is if I set a fake gateway/default route on the ethernet connection, something like 127.0.0.1 everything works just fine. It seems as though network manager will not even attempt to create the vpn connection if there is no gateway set.

Is this a bug? Where do I report it? How do I fix it?

2

1 Answer

This is a known feature/bug in NetworkManager dating back to 2013 there needs to be a gateway set even if it does nothing or is a fake IP.

1

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like