From: Jordan Johnston <johnstonljordan@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: WireGuard (Android) wg-quick down not working, WireGuard app can't bring down WireGuard tunnel
Date: Sat, 2 Dec 2017 19:44:39 -0500 [thread overview]
Message-ID: <CAKgnZ5yLcH45+a2N1qNMKqEhC3kPcS5uS_k6FNDi-AN7iUoXVw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
Hey list,
So after some help from the list, zx2c4 and on IRC
I've managed to get WireGuard working on my Google Pixel (Stock Rom). I've
been using it for a few hours now ~ after getting past a few initial
issues; I must say; WireGuard is fantastic!
Now, onto my current issue.
Currently, I have no problem enabling the wg tunnel on my device (using the
app or quick tile), however; I can't disable the tunnel once enabled (?)...
(using adb ... az = AzireVPN /data/misc/wireguard/az.conf ... the tunnel is
already running)
sailfish:/ # wg
interface: az
public key: (hidden)
private key: (hidden)
listening port: 42507
fwmark: 0x20000
peer: (hidden)
endpoint: 149.248.160.60:51820
allowed ips: 0.0.0.0/0, ::/0
latest handshake: 3 minutes, 50 seconds ago
transfer: 7.52 MiB received, 1.17 MiB sent
sailfish:/ # wg-quick down az
wg-quick: `az' is not a WireGuard interface
(note: the above keys I've made hidden, on my ouput they are there, minus
private key)
It's peculiar because the above does show the az interface via wg command
...
Likewise, the WireGuard app also fails when trying to bring down the tunnel
with the error message "Error bringing down WireGuard tunnel"... Yet the
tunnel is brought up no problem, from within the app, quick tile or
commandline (?).
According to the The help I was given on IRC - my config file appears to be
correct. (and is mostly working). So I'm not really sure what the problem
might be... I had thought there may have been a permission or selinux
denial somewhere - but I'm not seeing that in logcat;
logcat only shows the above wg-quick message
Jordan
[-- Attachment #2: Type: text/html, Size: 2176 bytes --]
next reply other threads:[~2017-12-03 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 0:44 Jordan Johnston [this message]
2017-12-03 1:06 ` Jason A. Donenfeld
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=CAKgnZ5yLcH45+a2N1qNMKqEhC3kPcS5uS_k6FNDi-AN7iUoXVw@mail.gmail.com \
--to=johnstonljordan@gmail.com \
--cc=wireguard@lists.zx2c4.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).