From: Gianluca Gabrielli <tuxmealux@protonmail.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Multiple peers
Date: Tue, 13 Mar 2018 13:07:44 -0400 [thread overview]
Message-ID: <sw07RFheJeAt1YhiYncjYl7au2RKQqmg4fMvgZBN91qBmUxoSGX24JamLXZrSqMC0yvRvz3koe24Li8ini3tEP1h_3j5VF5IFrYwcOMXI0A=@protonmail.com> (raw)
Hi everybody,
I have five peers, and I want that each peer can talk with all the other pe=
ers. Moreover let's say that one of these peer will acts as a server and as=
a gateway, while the other four will be only clients.=20
I wonder if I need to copy/paste all peers' public key on all the other pee=
rs' configuration, or I can just configure each peer to connect to the serv=
er and then allow peers talking with other peers passing through this serve=
r?
(Something similar to client-to-client option on OpenVPN)
I don't care about firewall rules to configure the server to NAT clients' c=
onnections, my question is just about wireguard configuration.
Cheers,
Gianluca
next reply other threads:[~2018-03-13 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 17:07 Gianluca Gabrielli [this message]
2018-03-13 17:35 ` condor+wireguard-mailinglist
2018-03-13 22:04 ` Tim Sedlmeyer
2018-03-15 15:05 ` Gianluca Gabrielli
2018-03-15 17:55 ` Germano Massullo
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='sw07RFheJeAt1YhiYncjYl7au2RKQqmg4fMvgZBN91qBmUxoSGX24JamLXZrSqMC0yvRvz3koe24Li8ini3tEP1h_3j5VF5IFrYwcOMXI0A=@protonmail.com' \
--to=tuxmealux@protonmail.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).