Hi, guys, and thanks for all of your work on this.
One suggestion -- you should add one note to the Wiki: Although the "preshared key" is optional, if a preshared key isn't used, the entire line must be deleted. If the line is present, but no key is supplied, the Wireguard instance will fail.
I wasted several hours before I figured this out, and I know others have as well.
rkershenbaum I've added a note to the wiki to highlight this point: https://wiki.libreelec.tv/configuration/wireguard
It seems like that the Host i.e Host = 185.210.30.121 in the example tutoral, cannot be a DDNS name.
How come?
Another thing that this does not seem to handle is ipv6 support. And this is added by default if you install wireguard via PiVPN.
Setting up a WireGuard VPN on the Raspberry Pi - Pi My Life Up
It seems like that the Host i.e Host = 185.210.30.121 in the example tutoral, cannot be a DDNS name. How come?
You're configurating a network interface not an application. NICs route traffic based on IP data and you're basically defining a static IP route to the other end of the tunnel. If you want to handle DDNS hostnames you need something at application level to resolve the hostname to an IP and update the WireGuard config. ConnMan watches the config files; I'm not sure if it can adjust the tunnel routing while the connection is active or it needs to stop/restart the connection first (should be simple to test though).
