Hey all,

I've recently set up my private VPN with Wireguard. I am running my local 
server behind a DSL router with a variable public IP address, accessible via 
dyndns and NAT, and several mobile clients (Android, Notebooks). 
Everything is working fine so far, except of one issue that I would like 
discuss here: 
Roaming doesn't work reliably when a device leaves or re-enters the home LAN, 
nor when the public IP address is changed by my ISP. The reason seems clear to 
me: In these cases both peers change their IP address simultaneously whereas 
the Wireguard protocol relies on only one address changing at a time.

My approach would be to shut down Wireguard on the clients as long as they are 
connected to their home network locally and to bring up the tunnel only when 
they leave the home network. Besides the roaming issue it  would be desirable 
to use the local connection when it is available rather than to take the detour 
over the internet. And it  should be done automatically so users need not 
remember to switch on/off VPN all the time.
My idea was to use Tasker to perform something like wg-quick up|down tun1 
accordingly, but the Wireguard command line tools wg and wg-quick don't seem to 
be available (anymore). In older forum posts I've seen that you can install 
them from the app settings, but in my version (v0.0.20190708) this option is 
not available.

Does anybody know about another solution? Or, as a question to the developers, 
would it be a big deal to bring back the command line feature?

Thanks, Tom




_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard

Reply via email to