From: Harsh Shandilya <me@msfjarvis.dev>
To: ND <iamlegendwtf@gmail.com>
Cc: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: Android Kernel Backend Bug
Date: Wed, 17 Jun 2020 13:38:12 +0530 [thread overview]
Message-ID: <69EEB742-6322-4BDF-BAA0-1872996E3D9E@getmailspring.com> (raw)
In-Reply-To: <CALO3qbuQms7XwmEYr-CpvspZuWzMqcRebfj8CH0zyYk6NmJZBw@mail.gmail.com>
On Jun 14 2020, at 11:59 pm, ND <iamlegendwtf@gmail.com> wrote:
> I've been trying to report an issue regarding the Android Kernel
> backend on
> irc freenode. I was told to email here.
>
> The problem:
> On LTE, my LTE carrier assigns two DNS servers, a private 10.x.x.x IP and
> 8.8.8.8.
> When using KERNEL BACKEND, establishing a tunnel doesn't override the
> carrier assigned DNS and DNS resolution goes through 8.8.8.8. All traffic
> still goes through the tunnel but the DNS does not respect the client
> config.
>
> On Userspace backend, the DNS i set in the client config (10.0.0.1
> i.e. my
> PiHole server) is respected.
>
> I'm on One Plus 6 latest Android Q. I've tried 2 kernels: Cleanslate and
> Radioactive kernel. Both support Wireguard.
>
I've CC'ed Jason who should have a better idea of what's going wrong
here. I sadly cannot confirm this on my end since I've upgraded to
Android R where Google has continued to butcher the command-line
tooling, thus breaking wg-quick.
prev parent reply other threads:[~2020-06-17 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALO3qbtXBYT2VRRit4tDC_k5aXmQWTj7n=qXbOBF=d0eZYO54w@mail.gmail.com>
2020-06-14 18:29 ` Fwd: " ND
2020-06-17 8:08 ` Harsh Shandilya [this message]
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=69EEB742-6322-4BDF-BAA0-1872996E3D9E@getmailspring.com \
--to=me@msfjarvis.dev \
--cc=Jason@zx2c4.com \
--cc=iamlegendwtf@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).