OK, it’s official; there’s issues with the Wireguard client, at least on the AR-750 running 3.005:
Using this page as a guide I verified my Wireguard server at home was set up properly. I plugged my configuration file into a(? the?) Wireguard Android client, and it works.
Plugging the very same file into the “Wireguard Client” dialog seems to accept it OK, but when I try to connect, it spins for a while then says “Timed Out”. Listening on either my eth0 or wg0 interfaces on my server show connectivity when trying to connect from the Android client, but nothing comes thru at all when trying from the AR-750’s client, which to me implies the issue could be DNS resolution; in any case it does not even attempt to ping my server (my server has an FQDN via dyn.com that has worked for years).
The bug is still there that if your (Wireguard, and maybe OpenVPN) connection fails, unless you purge your config files, your router’s clients get no connectivity even after a reboot
Here’s my wireguard client file:
Address = 192.168.12.2, fdd5:7dd4:34fa:770c::2/64
PrivateKey = <private key>
ListenPort = 21841
PublicKey = <public key>
Endpoint = <my server>.gotdns.com:51820
AllowedIPs = 0.0.0.0/0, ::/0
PersistentKeepalive = 180 # seconds
I’ll keep playing with it, removing keywords and spaces and such, but it does work with another client. I know that the AR-750 works with Azire, so maybe you’re bailing on a keyword (but I can’t see what that could be)?