From: i iordanov <iiordanov@gmail.com>
To: Aaron Jones <me@aaronmdjones.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Nested Wireguard tunnels not working on Android and Windows
Date: Mon, 1 Mar 2021 01:07:42 -0500 [thread overview]
Message-ID: <CAMS0tn0k=7aVstO7Nnn1zZDUypuE2sWidS3uT+04=7rs6+YjGQ@mail.gmail.com> (raw)
In-Reply-To: <65365aa6-cdd0-f9dc-f894-3a040ca596ae@aaronmdjones.net>
Hi Aaron, Frank,
Thanks for your replies. For some reason, gmail had decided Frank's
original reply was spam, I apologize for missing it. The first message
in response to mine I received was Aaron's. Frank, after retrieving
your message, yes you understanding is correct.
Yes, I have done packet capture and indeed, the setup works correctly
on Linux and Mac, whereas it does not work under Android and Windows.
What can I do to help diagnose, debug and/or resolve this issue?
Cheers and thanks!
iordan
On Sun, Feb 28, 2021 at 5:17 PM Aaron Jones <me@aaronmdjones.net> wrote:
>
> 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.
>
>
--
The conscious mind has only one thread of execution.
next prev parent reply other threads:[~2021-03-01 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 17:48 Nested Wireguard tunnels not working on Android and Windows i iordanov
2021-02-27 17:16 ` Frank Carmickle
2021-02-28 0:53 ` Aaron Jones
2021-03-01 6:07 ` i iordanov [this message]
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='CAMS0tn0k=7aVstO7Nnn1zZDUypuE2sWidS3uT+04=7rs6+YjGQ@mail.gmail.com' \
--to=iiordanov@gmail.com \
--cc=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).