Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Ole-Morten Duesund <olemd@glemt.net>
To: wireguard@lists.zx2c4.com
Subject: Re: NAT to NAT peers - 'EndPoint' IP data sharing among peers of the same key?
Date: Wed, 7 Apr 2021 09:50:31 +0200	[thread overview]
Message-ID: <69faf92d-4c03-8255-d816-3e6cac5d0bb9@glemt.net> (raw)
In-Reply-To: <20210407031540.6fbd6789@natsu>

On 07.04.2021 00:15, Roman Mamedov wrote:

> On Sat, 3 Apr 2021 06:27:40 +0200
> Giovanni Francesco <thelinuxguy@mail.com> wrote:
>
>> Hi, I am looking to understand if "EndPoint" IP data may be shared among peers within the tunnel?
>>
>> The question may sound confusing, let me explain my setup.
>>
>> I have a static IPv4 wireguard server (let's call it "A" peer) which has two downstream WG clients peers "B" and "C" on remote networks with dynamic WAN IPs (roaming).
>> In my current configuration all my clients "B" and "C" have a single peer "A" - therefore all traffic must always go to "A" - "A" is in a datacenter in another country.
>>
>> "B" and "C" have dynamic every changing IP "EndPoint" information, in my current setup this is not a problem because "A" is a static host.
>>
>> If "B" and "C" are connected to "A" - is it possible for me to make B and C peers of eachother without "EndPoint" ?
>> In other words, if B public key is a peer of C and vise versa would its connection to "A" share the IP addresses ("EndPoint" or where to go) downstream to "B" and "C" so they can establish direct connectivity or would traffic always need to continue to traverse via "A"?
> No, peer A will not tell peer B the current IP/port of peer C.
>
> Check out other tools, for instance Tinc can do this, but not WG.

There is also https://tailscale.com/blog/how-tailscale-works/ which does 
a bunch of magic to overcome NAT-problems.

My experience is that it works absolutely stunningly well.


- OM


      reply	other threads:[~2021-04-07  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03  4:27 Giovanni Francesco
2021-04-06 22:15 ` Roman Mamedov
2021-04-07  7:50   ` Ole-Morten Duesund [this message]

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=69faf92d-4c03-8255-d816-3e6cac5d0bb9@glemt.net \
    --to=olemd@glemt.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).