and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command) and in your specific case, what is the Ethernet or WiFi connection name you want to use and what is the UUID of your VPN connection?
P.S. If you enter a bit more details in your profile, we can also see which Desktop Environment you’re using, which CPU/GPU you have, …
Luckily I asked for the inxi as well as your Ethernet connection name is enp2s0 and that’s probably where you got stuck (Have a look at the network section of your own inxi as the ÌF means “InterFace” and that is network speak for “name”. )
so simply doing:
nmcli connection edit enp2s0
set connection.secondaries cabea9e2-922f-4381-a0cc-4ad95ea9e5ca
Thanks for your help but I’m not sure it’s correct. Here what I got with $ nmcli connection
NAME UUID TYPE DEVICE
VPN cabea9e2-922f-4381-a0cc-4ad95ea9e5ca vpn enp2s0
Internet 752d809c-a153-46d1-9a34-de12c37a64d7 ethernet enp2s0
enp2s0 isn’t the name but the device.
I tried to use UUID instead of name and it seems to be a little bit better but when i restart my computeur, my wired connexion is shutdown and I have to active it manually. But when i activate it, the VPN auto start. Any ideas ? And sorry for my english, it’s not my native tongue.