Re: Sharing peer data
> > 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 aa. -- Luiz Angelo Daros de Luca luizl...@gmail.com ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard
Re: Sharing peer data
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! ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard
Re: Sharing peer data
Thanks Jason, Yes, something very similar to tinc. I imagine having two or more static/known peers (redundancy) configured on every node. Once connected, they discover the others. It's good to know there is a GSoC for something like it. -- Luiz Angelo Daros de Luca luizl...@gmail.com ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard
Re: Sharing peer data
Hi Luiz, You could indeed arrange for something like this, either directly -- if both IPs are accessible or if A is able to punch a hole -- or relayed, if you can't establish a direct session. This is similar to what Tinc does. Namely, this falls in the category of, "making a full mesh from a partial mesh." I say, "you could", because currently this is something people are generally doing manually with WireGuard. However, there's a GSoC project for making a minimal mesh networking utility for WireGuard, which I hope pans out, and maybe even Tinc integration. So we'll see what happens in this space. Jason ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard
Sharing peer data
Hello, In a setup node A <> node B, node A <> node C, C might talk to B passing through A. Would it be possible that A could share B and C info (ip and pubkey) in other to them to talk to each other directly? It would be similar to ip redirect. Node A must be trusted by both for that. Regards, -- Luiz Angelo Daros de Luca luizl...@gmail.com ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard
