Well… first of all thanks for the explanation regarding ip_forward.conf
My VPN provider gives me this to connect to a group of their servers I tend to use:
[Interface]
Address = 10.173.72.95
PrivateKey = HUKXeSPCgjBgICylEXFBeQGHJiTxhYlOJcECZrWQucrd
MTU = 1320
DNS = 10.128.0.1
[Peer]
PublicKey = CUpwVFSbfscpbATZUPjtfhgfknmsZQgEbvRjLVqlasz=
PresharedKey = otltlirAiTLMEsEqfYyrwCyJtaKgQLhnVVLxgcjYELR=
Endpoint = nl3.vpn.airdns.org:1637
AllowedIPs = 0.0.0.0/0
PersistentKeepalive = 15
All keys have been substituted by me with random ones in the above, for obvious reasons.
Now, this very same configuration file works perfectly on a Vero4K+ by following this guide:
ssh to your Vero
first we install wireguard and openresolv, which you need if you want to provide a DNS in your confsudo apt install wireguard-tools sudo apt install openresolv
now we configure the client (you can name wg0 however you want, just change it accordingly in the following):
sudo nano /etc/wireguard/wg0.conf
paste the config, save and exit nano
you can now establish and test the connection withsudo wg-quick up wg0 sudo wg
Apart from some slight complication in the service creation part later on, it’s all absolutely straightforward. I took my VPN provider’s config, copied it as wg0.conf and it was working. The beauty of WireGuard (among other things) is that it easy to configure. But here on CoreELEC it doesn’t seem the case, unless I am missing something major.
When using connmanctl method you lose the ability to use a load balanced endpoint (the nl3.vpn.airdns.org thing selects a server among the ones available based on current load), with the method I’m trying to use here… I can’t seem to make it work.
Maybe it’s the “just enough Linux for” thing, maybe Vero has a more complete distribution included? I don’t have the foggiest idea, I’m just sorry that I can’t manage to use WireGuard, which is something I foolishly gave for granted when I bought the Ugoos. Not complaining or whining, it’s on me.
EDIT: at least I see even devs were not happy about connman implementation Wireguard difficulties [SOLVED] - #46 by Ray but since 2022 things have quieted down on this front, it seems. @Ray