Development discussion of WireGuard
 help / color / mirror / Atom feed
* WireGuardNT: Tunnels cannot be "nested"
@ 2021-08-23 10:21 David Lönnhager
  2021-09-16  9:32 ` David Lönnhager
  0 siblings, 1 reply; 2+ messages in thread
From: David Lönnhager @ 2021-08-23 10:21 UTC (permalink / raw)
  To: wireguard

Hello,

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:

[Peer]
Endpoint = A:51820
AllowedIPs = B/32
[Peer]
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?

Thank you,
David

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-09-16  9:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-23 10:21 WireGuardNT: Tunnels cannot be "nested" David Lönnhager
2021-09-16  9:32 ` David Lönnhager

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).