From: Dana White <danabw@hotmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: RE: Potential bug in Android app - Create from scratch flow
Date: Sun, 5 Apr 2020 22:55:01 +0000 [thread overview]
Message-ID: <MWHPR17MB16480A2D637D253F9A5BCBBAD0C50@MWHPR17MB1648.namprd17.prod.outlook.com> (raw)
In-Reply-To: <CAHmME9q0sbmNpYB5-ZWaT2MUQq_SPdsF9jJ9frkbffwN+RvP7w@mail.gmail.com>
Thanks. Using the config was just to test the import process on Android w/a known good config, deleted thereafter.
From your reply sounds like you haven't seen this issue w/the current version of the app? Are you able to manually create and use a new tunnel on the Android app successfully?
I had another member of the EdgeRouter community note that he had what he thought was a similar problem recently w/the Android app but didn't take the time to follow upon it.
I'll do as you request and get back.
Dana
-----Original Message-----
From: Jason A. Donenfeld <Jason@zx2c4.com>
Sent: Sunday, April 5, 2020 2:54 PM
To: Dana White <danabw@hotmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Potential bug in Android app - Create from scratch flow
> Finally (thanks to someone on #wireguard irc) I tried imported the exact same config into the app, and it worked immediately.
Don't use the same config from two devices. One device :: one private key.
> It looks like there may be a problem w/the manual entry process. At least that was my experience, repeatedly. App is current version, just installed for the first time two days ago.
Create it manually, and then export it to a zip. Look in the zip and see if there's any difference between that file and the one you imported from the windows app.
next prev parent reply other threads:[~2020-04-05 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 15:58 Dana White
2020-04-05 21:53 ` Jason A. Donenfeld
2020-04-05 22:55 ` Dana White [this message]
2020-04-05 23:23 ` Dana White
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=MWHPR17MB16480A2D637D253F9A5BCBBAD0C50@MWHPR17MB1648.namprd17.prod.outlook.com \
--to=danabw@hotmail.com \
--cc=Jason@zx2c4.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).