From: "Thomas Börner" <boerner@t-online.de>
To: "Yağmur Oymak" <yagmur.oymak@gmail.com>,
boerner@t-online.de, wireguard@lists.zx2c4.com
Subject: Re: Wireguard command line tools for Android
Date: Fri, 09 Aug 2019 10:47:18 +0200 [thread overview]
Message-ID: <ADD7E5C3-E762-47A5-BBE1-9328D7C8DA52@t-online.de> (raw)
In-Reply-To: <6910a3cab7c5cdfe32de3b61095c7cc47e0702b2.camel@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1370 bytes --]
Thanks for the clarification!
But this also means that a Tasker workaround would not be feasible for a common user.
Thus, renewing the binding via DNS when the tunnel is broken would be most desirable, as I already proposed.
Am 7. August 2019 12:52:19 MESZ schrieb "Yağmur Oymak" <yagmur.oymak@gmail.com>:
>On Sat, 2019-07-27 at 18:01 +0200, boerner@t-online.de wrote:
>> 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?
>
>Hey,
>
>The command line tools were not removed. If you are using the Go
>userspace backend (the app will indicate this in settings, together
>with the version information) they will not be available. The tools
>control the kernel backend and require root access. Thus they are only
>available if you are running a custom kernel with WireGuard support and
>have root access.
>
>--
>Yagmur Oymak
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
[-- Attachment #1.2: Type: text/html, Size: 1771 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-08-25 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 16:01 boerner
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 [this message]
2019-08-09 8:52 ` Thomas Börner
Reply instructions:
You may reply publicly 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ADD7E5C3-E762-47A5-BBE1-9328D7C8DA52@t-online.de \
--to=boerner@t-online.de \
--cc=wireguard@lists.zx2c4.com \
--cc=yagmur.oymak@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).