WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: Harsh Shandilya <me@msfjarvis.dev>
To: Jose Marinez <jedi_papi@yahoo.com>
Cc: WireGuard Mailing List <wireguard@lists.zx2c4.com>
Subject: Re: Shouldn't devices tethered to a device using Wireguard share the same IP?
Date: Wed, 20 May 2020 23:23:00 +0530
Message-ID: <7CE4203F-F77E-479D-8F0B-E67A366F1EB3@getmailspring.com> (raw)
In-Reply-To: <1587211445.2302354.1589995651547@mail.yahoo.com>



On May 20 2020, at 10:57 pm, Jose Marinez <jedi_papi@yahoo.com> wrote:

> Hi Guys,
>  
> Can you tell me if this is working as it should?...
>  
> I have a phone with Wireguard on. I share the connection via
> tethering/hotspot. When I check the IP on the tethered device I don't
> see the same IP as my Wireguard endpoint. What I do see is an IP from
> the phone's mobile network, the one running Wireguard. 
>  
> Is this right? Does this mean that traffic from that tethered device
> not using the Wireguard connection? I'm confused.
>  
>  
> Thanks,
> Jose
>  

At least on Android, tethering data is *not* routed through your VPN. If
you want that to happen, you will have to use the WireGuard kernel
module which requires a rooted device and a custom kernel. On some
supported devices
(https://github.com/WireGuard/android-wireguard-module-builder/tree/master/kernels)
you can use root access to install the required module automatically
through the app, on your stock kernel.

Harsh

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1587211445.2302354.1589995651547.ref@mail.yahoo.com>
2020-05-20 17:27 ` Jose Marinez
2020-05-20 17:53   ` Harsh Shandilya [this message]
2020-05-20 18:40     ` Jose Marinez
     [not found]       ` <81BFEC8F-2985-447E-9B08-5671682DBD3E@43.yt>
2020-05-20 20:53         ` Jose Marinez
2020-05-21  7:05           ` Harsh Shandilya
2020-05-21 14:22             ` Jose Marinez
2020-05-21 14:28               ` Harsh Shandilya
2020-05-21 23:20                 ` Jose Marinez
     [not found] <1911672182.4980335.1590508735704@mail.yahoo.com>
2020-05-26 16:03 ` Harsh Shandilya

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=7CE4203F-F77E-479D-8F0B-E67A366F1EB3@getmailspring.com \
    --to=me@msfjarvis.dev \
    --cc=jedi_papi@yahoo.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

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git