From: mikma.wg@lists.m7n.se
To: Julian Orth <ju.orth@gmail.com>, wireguard@lists.zx2c4.com
Subject: Re: Multiple VPN connections on Android
Date: Tue, 26 Mar 2019 20:35:17 +0100 [thread overview]
Message-ID: <1aad1b45-8174-79c3-f62b-84462e0c2baa@m7n.se> (raw)
In-Reply-To: <75dc1198-7727-f342-2756-a160f3f3f994@gmail.com>
On 2019-03-26 15:17, Julian Orth wrote:
> Hello list,
>
> I'm currently using WireGuard on Android for two purposes:
>
> 1. Routing all traffic via a commercial VPN provider to protect myself on
> open wireless networks.
> 2. Connecting to my home network.
>
> Unfortunately WireGuard on Android does not allow me to do both of these
> things at the same time. I assume this is because VpnService [1] only allows 1
> VPN connection at a time.
Can't you add the peer for your home network to the same configuration
(tun device) as the peer for the commercial VPN provider? It seems a
straight forward solution to me if you are okay with the IP addresses
assigned by the VPN provider.
>
> Has any thought been put into emulating multiple tun devices in user space?
I don't see why you would need multiple tun devices. It is possible to
add multiple IPv4 and IPv6 addresses to the tun device, but there may be
a problem with the source address selection. Linux allows specifying a
preferred address for each route, but it isn't possible in the Android
API AFAIK. If you have a rooted device then you can potentially update
the routing tables with the preferred source address for each VPN route.
/Mikma
>
> Julian
>
> [1] https://developer.android.com/reference/android/net/VpnService.html
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-04-05 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 14:17 Julian Orth
2019-03-26 19:35 ` mikma.wg [this message]
[not found] ` <911c5ed5-0bf8-80bb-cf15-7b2c6ee896fa@m7n.se>
2019-04-07 10:37 ` Julian Orth
2019-04-07 10:55 ` Matthias Urlichs
2019-04-08 1:39 ` Jason A. Donenfeld
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=1aad1b45-8174-79c3-f62b-84462e0c2baa@m7n.se \
--to=mikma.wg@lists.m7n.se \
--cc=ju.orth@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).