From: "David Lönnhager" <firstname.lastname@example.org>
Subject: WireGuardNT: Tunnels cannot be "nested"
Date: Mon, 23 Aug 2021 12:21:30 +0200 [thread overview]
Message-ID: <CAFiEPQu-w-ZX-TMiriGpK2h4_WSGs+5mzq_5PbhbjK1yyncCbA@mail.gmail.com> (raw)
I'm trying to connect to one peer/endpoint via another peer. Using
wireguard-go, or using WireGuard in the Linux kernel, this could be
accomplished with a configuration kind of like this one:
Endpoint = A:51820
AllowedIPs = B/32
Endpoint = B:51820
AllowedIPs = 0.0.0.0/0
When I try this setup with WireGuardNT (0.4), it seems as if B is
being connected to directly (outside of any tunnel), even if I route
"B" through the WireGuard interface.
Are routes using the interface being ignored
(https://git.zx2c4.com/wireguard-nt/tree/driver/socket.c#n213), and is
this the reason why the above no longer seems to work?
Is there any chance that this will change?
next reply other threads:[~2021-08-23 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 10:21 David Lönnhager [this message]
2021-09-16 9:32 ` David Lönnhager
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 \
* 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).