From: mikma.wg@lists.m7n.se
To: i iordanov <iiordanov@gmail.com>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Nested Wireguard tunnels not working on Android and Windows
Date: Tue, 2 Mar 2021 15:31:36 +0100 [thread overview]
Message-ID: <11abae81-4a87-9016-69a8-e62351a0deba@fox.m7n.se> (raw)
In-Reply-To: <CAMS0tn2FXkzFHgMgkDwYvD2Fhrxb_PjMNDuV54sL9-ZhTijS7A@mail.gmail.com>
On 2021-03-01 21:09, i iordanov wrote:
> Hi Frank,
>
> On Mon, Mar 1, 2021 at 9:42 AM Frank Carmickle <frank@carmickle.com> wrote:
>> Maybe it's a bug and not a feature? It seems to me that you would have no way of setting the MTU on the inner tunnel.
> That's true - other than inefficient packet fragmentation, is there
> anything else that would be an issue?
It's possible to configure the MTU for each route on Linux. (Obviously
you can't use the extremely simple wg-quick script for this.)
>
>> Is there a reason why you can't try multiple interfaces?
> I cannot bring up more than a single interface on Android. I am not
> sure about interface management on Windows with wg.exe, but
> wireguard.exe certainly does not permit multiple interfaces to be
> brought up.
The WireGuard app on Android also can't use a VPN address as the source
of WireGuard packets. Only non-VPN addresses are supported.
Which means currently the WireGuard app on Android can't be used for
nested tunnels.
next prev parent reply other threads:[~2021-03-02 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 17:48 i iordanov
2021-02-27 17:16 ` Frank Carmickle
2021-02-28 0:53 ` Aaron Jones
2021-03-01 6:07 ` i iordanov
2021-03-01 14:44 ` Frank Carmickle
2021-03-01 20:09 ` i iordanov
2021-03-02 14:31 ` mikma.wg [this message]
2021-03-04 8:56 ` Matthias Urlichs
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=11abae81-4a87-9016-69a8-e62351a0deba@fox.m7n.se \
--to=mikma.wg@lists.m7n.se \
--cc=iiordanov@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).