From: Aaron Jones <me@aaronmdjones.net>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Nested Wireguard tunnels not working on Android and Windows
Date: Sun, 28 Feb 2021 00:53:41 +0000 [thread overview]
Message-ID: <65365aa6-cdd0-f9dc-f894-3a040ca596ae@aaronmdjones.net> (raw)
In-Reply-To: <E8F8664E-3C8A-45B9-B9B8-1A1E2873289B@carmickle.com>
[-- Attachment #1.1: Type: text/plain, Size: 467 bytes --]
On 27/02/2021 17:16, Frank Carmickle wrote:
> Iordan,
>
> You say that it's possible to run a nested configuration on
> Linux and Macos with just a single interface each. Have you
> done a packet capture to prove that that is in fact what is
> happening? That doesn't seem like how it would act given the
> design goals.
Nesting (Using one of Peer A's AllowedIPs as Peer B's Endpoint) does
work within the same WireGuard interface, at least on Linux.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-28 22:14 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 [this message]
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
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=65365aa6-cdd0-f9dc-f894-3a040ca596ae@aaronmdjones.net \
--to=me@aaronmdjones.net \
--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).