WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: boerner@t-online.de
To: wireguard@lists.zx2c4.com
Subject: Wireguard command line tools for Android
Date: Sat, 27 Jul 2019 18:01:56 +0200
Message-ID: <5549622.se0SCevcK7@majestix.boerner.local> (raw)

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

             reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 16:01 boerner [this message]
2019-08-05 21:28 ` David Kerr
2019-08-06  7:17   ` boerner
2019-08-06 12:33     ` David Kerr
2019-08-06 13:08       ` boerner
2019-08-06 13:18       ` Joachim Lindenberg
2019-08-07 10:52 ` Yağmur Oymak
2019-08-09  8:47   ` Thomas Börner
2019-08-09  8:52   ` Thomas Börner

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5549622.se0SCevcK7@majestix.boerner.local \
    --to=boerner@t-online.de \
    --cc=wireguard@lists.zx2c4.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox