From: "B. Reino" <reinob@bbmk.org>
To: wireguard@lists.zx2c4.com
Subject: Re: Android traffic not being sent over tunnel when using kernel backend
Date: Wed, 5 Dec 2018 19:50:20 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.1812051945140.28379@ertraobtra> (raw)
In-Reply-To: <1543894515.2362814.1597906872.33D7BAA3@webmail.messagingengine.com>
On Mon, 3 Dec 2018, BBreeziN wrote:
> I recently set up a WireGuard tunnel between my Android phone and
> Ubuntu Server at home. When using the WireGuard app without root
> granted to it, the userspace implementation works as expected. I get
> the key icon in the status bar on Android and my traffic is being
> routed through the tunnel.
> I then rooted my device, installed the ElementalX kernel (with WireGuard
> support), and upon granting the WireGuard app root access, it indicates
> the kernel module backend is being used. However, now when connecting my
> tunnel using the same settings, my traffic is not being routed through
> the tunnel. I can see this by visiting a site like whoer.net and which
> reveals my carrier WAN IP, not my IP of my home ISP.
> The tunnel seems to be active using the kernel module as I can ping the
> phone (192.168.2.2) from the server (192.168.2.1). I can also ping
> 192.168.2.1 from my phone.
> Any idea why the web traffic is being routed through the tunnel ONLY
> when I use the Go userspace backend? Thanks for the help!
> WireGuard for Android v0.0.20181001
> Kernel module backend v0.0.2018119
>
> WireGuard Ubuntu Bionic v0.0.20181119
After reading your message I decided to (finally) install ElementalX on my
Oneplus 6. I then tested Wireguard (v0.0.20181103, from F-Droid) using the
kernel module backend (v0.0.20180809).
It all worked perfectly, including the routing. I tested also with "whats
my ip" (a few hits on google), and it always showed the IP of my server (a
VPS).
The server is running debian stretch with wireguard 0.0.20181119-1 (taken
from debian unstable).
Good luck!
--
Bernardo Reino
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2018-12-06 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 3:35 Android traffic not being sent over tunnel when using kernel backend BBreeziN
2018-12-05 18:50 ` B. Reino [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=nycvar.QRO.7.76.1812051945140.28379@ertraobtra \
--to=reinob@bbmk.org \
--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).