Nested Wireguard tunnels not working on Android and Windows

[Frank Carmickle]

Iordan,

> On Mar 1, 2021, at 1:07 AM, i iordanov <iiordanov at gmail.com> wrote:
> 
> 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.

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.

> What can I do to help diagnose, debug and/or resolve this issue?

Is there a reason why you can't try multiple interfaces?

--FC

> Cheers and thanks!
> iordan
> 
> 
> On Sun, Feb 28, 2021 at 5:17 PM Aaron Jones <me at 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.