Fwd: Android Kernel Backend Bug

Fwd: Android Kernel Backend Bug

[ND]

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

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.

[-- Attachment #2: Screenshot_20200614-205517~2.jpg --]
[-- Type: image/jpeg, Size: 212654 bytes --]

Re: Android Kernel Backend Bug

[Harsh Shandilya]

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.