wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: "Eric Light" <eric@ericlight.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Android: more than one tunnel
Date: Thu, 15 Jul 2021 10:09:36 +1200	[thread overview]
Message-ID: <d994accd-d1a9-4f9a-bbf9-d6b99036b177@www.fastmail.com> (raw)
In-Reply-To: <e8e94195-b1f0-df62-4393-929f20f762a3@spam-free.eu>

Hi Chris!

I don't have any experience with the Android implementation specifically... but most likely, your two tunnels have overlapping AllowedIPs ranges.  When this happens, bringing up the second interface will override the routing created by the first interface.

Most commonly, this happens when someone configures both interfaces with AllowedIPs =  To fix this problem, make sure there's no overlap of AllowedIPs in your tunnel definitions.

I hope this helps  :)

(my apologies if the problem is something Android-specific that I don't know about)


Q: Why is this email five sentences or less?
A: http://five.sentenc.es

On Wed, 14 Jul 2021, at 17:49, Chris 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

  parent reply	other threads:[~2021-07-14 22:10 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
2021-07-14 22:09     ` Eric Light [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d994accd-d1a9-4f9a-bbf9-d6b99036b177@www.fastmail.com \
    --to=eric@ericlight.com \
    --cc=wireguard@lists.zx2c4.com \


* 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).