From: Simon McNair <simonmcnair@gmail.com>
To: Chris <wireguard@spam-free.eu>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Android: more than one tunnel
Date: Wed, 14 Jul 2021 10:06:22 +0100 [thread overview]
Message-ID: <b87f5a75-40e6-a55e-ae5c-74040748a624@gmail.com> (raw)
In-Reply-To: <e8e94195-b1f0-df62-4393-929f20f762a3@spam-free.eu>
I think this is a limitation of android, not wireguard.
https://developer.android.com/guide/topics/connectivity/vpn
<https://developer.android.com/guide/topics/connectivity/vpn>
"
There’s only one active service per user or profile. Starting a new
service, automatically stops an existing service"
Sent again due to being formatted as HTML rather than text and/or
forgetting to cc the list.
Simon
On Wed, 14 Jul 2021, 06:54 Chris, <wireguard@spam-free.eu
<mailto:wireguard@spam-free.eu>> wrote:
I have two distinct tunnels defined on Android.
However, I can only toggle between the two. I cannot have both
activated at the
same time.
I need both connections.
Am I missing anything?
Why not several tunnels with several wg servers???
Why is this being prevented?
BR
Chris
next prev parent reply other threads:[~2021-08-08 23:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1601114111.20018.wireguard@lists.zx2c4.com>
2020-09-26 10:40 ` lineageos 17.1after autostart on boot tunnel not functioning Chris
2020-10-01 14:42 ` Chris
2021-07-14 5:49 ` Android: more than one tunnel Chris
2021-07-14 9:06 ` Simon McNair [this message]
2021-07-14 22:09 ` Eric Light
2021-07-14 23:55 ` iiiiiiiiiiii
2021-07-15 6:25 ` Chris
2020-10-01 15:24 ` lineageos 17.1 no incoming Chris
2020-10-05 13:51 ` wg-quick up (on linux) fails in case of several default routes Chris
2020-10-06 12:20 ` Jason A. Donenfeld
2020-10-06 13:33 ` Chris
2020-10-06 13:47 ` Jason A. Donenfeld
2020-10-06 13:54 ` Chris
2020-10-06 13:58 ` Jason A. Donenfeld
2020-10-06 17:51 ` Chris
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=b87f5a75-40e6-a55e-ae5c-74040748a624@gmail.com \
--to=simonmcnair@gmail.com \
--cc=wireguard@lists.zx2c4.com \
--cc=wireguard@spam-free.eu \
/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).