From: Luiz Angelo Daros de Luca <luizluca@gmail.com>
To: ST <smntov@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Sharing peer data
Date: Mon, 16 Apr 2018 01:47:01 +0000 [thread overview]
Message-ID: <CAJq09z6sHzLPkcCMmwOm0dyA2yS1CY0z-Mqgs9px04L8gMfdxA@mail.gmail.com> (raw)
In-Reply-To: <1523786895.1990.5.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
>
> 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?
In my point of view, it is something that all nodes must agree to accept (a
non-default option). Of course, if node A wants to measure traffic, it
ahould not allow it, forcing all traffic from B to C to pass through it.
I imagine something like:
Node A: hey node B, I noticed that you are sending traffic to another
remote node (node C). You can continue to send traffic through me but, in
parallel, could you please try to contact node C directly? It is currently
using ip x.x.x.x and its pubkey is aaaaaa.
--
Luiz Angelo Daros de Luca
luizluca@gmail.com
[-- Attachment #2: Type: text/html, Size: 1347 bytes --]
prev parent reply other threads:[~2018-04-16 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 19:16 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
2018-04-16 1:47 ` Luiz Angelo Daros de Luca [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=CAJq09z6sHzLPkcCMmwOm0dyA2yS1CY0z-Mqgs9px04L8gMfdxA@mail.gmail.com \
--to=luizluca@gmail.com \
--cc=smntov@gmail.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).