From: Love4Taylor <love4taylor.me@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Google Play can't Download through Kernel module backend
Date: Mon, 22 Oct 2018 09:17:56 +0800 [thread overview]
Message-ID: <CAD6UttB+_G4RY-TwyJ7w6rX-wKqqRqds0B9hMVvFPfjNHvwtgg@mail.gmail.com> (raw)
Hi,
I recently discovered that when I use the Kernel module backend,
Google Play will always be stuck in Downloading, I got the following
logcat, but everything works fine when using Go module backend
(Android VPN).
D DownloadManager: [558] Starting
W DownloadManager: [514] Stop requested with status HTTP_DATA_ERROR:
SSL handshake aborted: ssl=0x766f2a4008: I/O error during system call,
Connection reset by peer
D DownloadManager: [514] Finished with status WAITING_TO_RETR
D DownloadManager: [558] Starting
W DownloadManager: [555] Stop requested with status HTTP_DATA_ERROR:
failed to connect to r1---sn-3qqp-ioqsl.gvt1.com/27.85.180.172 (port
443) from /10.0.0.101 (port 49253) after 20000ms
D DownloadManager: [555] Finished with status HTTP_DATA_ERROR
I think it should not be a server problem, even if I use the free
server provided by TunSafe, it is the same problem. It seems that the
DownloadManager called by Google Play has not passed Wireguard at
all(10.0.0.101 is my LAN IP). Then I did the following test.
Kernel module backend + Router blocks Google domain name: Google Play
stuck in Downloading, the log is the same as above.
Go module backend + Router blocks Google domain name: Everything works
fine, no error log.
Kernel module backend + Router does not block Google domain name:
Everything works fine, no error log.
My Phones: OG Pixel/Nexus6 (Both are Android 9)
The link is route etc. on my phone: http://ix.io/1n8q
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2018-11-04 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 1:17 Love4Taylor [this message]
2018-11-04 17:18 ` Tushar Pankaj
2018-11-04 17:43 ` Jason A. Donenfeld
2018-11-04 18:07 ` Tushar Pankaj
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=CAD6UttB+_G4RY-TwyJ7w6rX-wKqqRqds0B9hMVvFPfjNHvwtgg@mail.gmail.com \
--to=love4taylor.me@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).