From: Matthew Letnaunchyn <matt@letnaunchyn.com>
To: wireguard@lists.zx2c4.com
Subject: Re: wireguard-android broken after update to Android 10
Date: Fri, 6 Sep 2019 19:11:43 -0500 [thread overview]
Message-ID: <CAFF9ZB8Afvem6ecbuamwS-hRn=9_MWFMT4GD2sjgLjaM+4Q6Ew@mail.gmail.com> (raw)
In-Reply-To: <CAPk0gXpes_ALUUug2BJc-x_cRNPtV1kNn3T1b2WnRkv-fn7izw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1240 bytes --]
I'm on a pixel 3a xl with Android 10 and have no issues either. The only
quirk is the notification shade shortcut has occasionally refused to start
the connection but starting the vpn within the app works fine. I run a
freebsd 12 and an Ubuntu 18.04 LTS server. Both work with Android 10 as
expected. I would second the recommendation to double check the private DNS
settings but am happy to help troubleshoot if I can.
Matt
On Fri, Sep 6, 2019, 5:01 PM Frederick Ding <frederick@frederickding.com>
wrote:
> That’s right, works for me. And I was previously on the Q betas and
> WireGuard from the Play Store continued to work.
>
> On Fri, Sep 6, 2019 at 23:59 Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
>> On Fri, Sep 6, 2019, 16:55 Frederick Ding <frederick@frederickding.com>
>> wrote:
>>
>>> Pixel 3 user here on Android 10. Have you checked
>>>
>>
>> Just to be certain: is the implication here that you have a P3+AndroidQ
>> and don't face any trouble using WireGuard?
>>
> --
> Regards,
> Frederick Ding | frederick@frederickding.com
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 2647 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-09-11 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 5:11 Cory Fields
2019-09-06 21:07 ` Frederick Ding
2019-09-06 21:58 ` Jason A. Donenfeld
2019-09-06 22:00 ` Frederick Ding
2019-09-07 0:11 ` Matthew Letnaunchyn [this message]
2019-09-09 14:36 ` Cory Fields
2019-09-07 12:36 Salvatore LaMendola
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='CAFF9ZB8Afvem6ecbuamwS-hRn=9_MWFMT4GD2sjgLjaM+4Q6Ew@mail.gmail.com' \
--to=matt@letnaunchyn.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).