wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Giovanni Francesco <thelinuxguy@mail.com>
To: wireguard@lists.zx2c4.com
Subject: NAT to NAT peers - 'EndPoint' IP data sharing among peers of the same key?
Date: Sat, 3 Apr 2021 06:27:40 +0200	[thread overview]
Message-ID: <trinity-3510980c-c0ee-4d02-bcf5-8b7d2a708cda-1617424060455@3c-app-mailcom-lxa15> (raw)

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"?

Thanks!

             reply	other threads:[~2021-04-06 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03  4:27 Giovanni Francesco [this message]
2021-04-06 22:15 ` NAT to NAT peers - 'EndPoint' IP data sharing among peers of the same key? Roman Mamedov
2021-04-07  7:50   ` Ole-Morten Duesund

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=trinity-3510980c-c0ee-4d02-bcf5-8b7d2a708cda-1617424060455@3c-app-mailcom-lxa15 \
    --to=thelinuxguy@mail.com \
    --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).