From: ST <smntov@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Sharing peer data
Date: Sun, 15 Apr 2018 13:08:15 +0300 [thread overview]
Message-ID: <1523786895.1990.5.camel@gmail.com> (raw)
In-Reply-To: <CAHmME9qpEVW3AwDPCUSUA_A4DJi+oTGoMX4V3fVyHk7aXsAZ6Q@mail.gmail.com>
On Sun, 2018-04-15 at 01:15 +0200, Jason A. Donenfeld wrote:
> Hi Luiz,
>
> You could indeed arrange for something like this, either directly --
> if both IPs are accessible
Which IPs do you mean here? Public IPs or private VPN IPs (i.e. those
defined within WireGuard configuration)? I got an idea how to do that
using SFTP... I'll write about it in a separate email...
Just one question: let's assume B and C got the required information
about each other's IPs/public keys from A. Will they now communicate
directly without relying on A in whatever way?... It is important to
know for the case when A is a server with metered paid traffic... Will
the communication between B and C affect the traffic of A or not?
Thank you!
next prev parent reply other threads:[~2018-04-15 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 19:16 Sharing peer data Luiz Angelo Daros de Luca
2018-04-14 23:15 ` Jason A. Donenfeld
2018-04-15 3:18 ` Luiz Angelo Daros de Luca
2018-04-15 10:08 ` ST [this message]
2018-04-16 1:47 ` Luiz Angelo Daros de Luca
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=1523786895.1990.5.camel@gmail.com \
--to=smntov@gmail.com \
--cc=Jason@zx2c4.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