From: Frederick Ding <frederick@frederickding.com>
To: lists@coryfields.com
Cc: wireguard@lists.zx2c4.com
Subject: Re: wireguard-android broken after update to Android 10
Date: Fri, 6 Sep 2019 23:07:56 +0200 [thread overview]
Message-ID: <CAPk0gXqPUHS0ufEj7CEDHaf+_KDbzKW8Et8yHO3mtjR9SEUNwQ@mail.gmail.com> (raw)
In-Reply-To: <CAApLimgrYEmnRXNuOdnkPW=uihe325z5xzBAGGHZx-YB0L9CCQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1306 bytes --]
Pixel 3 user here on Android 10. Have you checked whether all packets are
not getting through, or whether it's just appearing that way due to DNS
issues? Maybe try deactivating the Private DNS (which may use DNS over
HTTP) setting in Network & Internet settings and see if that helps? Or try
using Hurricane Electric's net tools app to try pinging an IP address by
number to see where things are breaking...
On Fri, Sep 6, 2019, 21:19 Cory Fields <lists@coryfields.com> wrote:
> Today I updated my Pixel 3 to Android 10 and my wireguard vpn is no longer
> functional. Everything appears to be working fine, just no connections.
> It's a very straightforward ipv4 setup with a Debian host on the other side.
>
> It seems maybe I'm not alone:
>
> https://old.reddit.com/r/WireGuard/comments/bnx4yy/wireguard_tunnel_broken_on_android_q_beta/
>
> Might there be some non-obvious new security setting that needs to be
> turned off (or granted) after the update?
>
> I'm afraid I don't have much other useful information to provide here, but
> I can send a log file from the android client off-list if it would be
> helpful.
>
> Regards,
> Cory Fields
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 2078 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-06 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 5:11 wireguard-android broken after update to Android 10 Cory Fields
2019-09-06 21:07 ` Frederick Ding [this message]
2019-09-06 21:58 ` Jason A. Donenfeld
2019-09-06 22:00 ` Frederick Ding
2019-09-07 0:11 ` Matthew Letnaunchyn
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=CAPk0gXqPUHS0ufEj7CEDHaf+_KDbzKW8Et8yHO3mtjR9SEUNwQ@mail.gmail.com \
--to=frederick@frederickding.com \
--cc=lists@coryfields.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).