From: Denis Kisselev <denis@dkisselev.net>
To: John Smith <johnsmith1@riseup.net>,
WireGuard List <wireguard@lists.zx2c4.com>
Subject: RE: WireGuard server and multiple clients
Date: Tue, 20 Nov 2018 03:40:38 +0000 [thread overview]
Message-ID: <CY4PR14MB1141B76AC8CD7C2944938FA2A2D90@CY4PR14MB1141.namprd14.prod.outlook.com> (raw)
In-Reply-To: <09ef4c2c-a445-1183-d4c6-1a6ca0e0cb41@riseup.net>
[-- Attachment #1.1: Type: text/plain, Size: 1886 bytes --]
Nope,
Wireguard should work with multiple clients by default. You just have to manually add the public key and assign an IP for each one.
Whether any specific configuration is “recommended” really depends on your exact use-case and assessment of the other options that are available to you.
Wireguard can be a great VPN to let friends and family connect to you, but so can OpenVPN or even Hamachi.
Commercial WG VPN’s are still sparse primarily because the project is still relatively young. The providers need to write custom integrations to tie wireguard servers into their billing and client key generation systems, and many may not trust it yet because the codebase is evolving so much.
________________________________
From: WireGuard <wireguard-bounces@lists.zx2c4.com> on behalf of John Smith <johnsmith1@riseup.net>
Sent: Monday, November 19, 2018 9:30:00 AM
To: WireGuard List
Subject: WireGuard server and multiple clients
Hello,
If I were to set up a WireGuard server and have multiple clients
connecting to it, is there anything I need to be aware of? Specifically,
I am looking to understand if this is recommended as I already see
commercial offering of WireGuard - but not by all providers - so I was
wondering if there are any caveats to this approach.
For added context, I was managing a VPN server for my family and friends
but now I am considering switching to WireGuard.
Thanks.
- J Smith
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.zx2c4.com%2Fmailman%2Flistinfo%2Fwireguard&data=02%7C01%7C%7C682833c00bdb4550ea6008d64e523de3%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636782512459091879&sdata=KARAdd2N0g93ovqzUe8adi3ek%2FOWBZRTWQHllLVO8qs%3D&reserved=0
[-- Attachment #1.2: Type: text/html, Size: 4130 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2018-11-20 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 17:30 WireGuard server and multiple clients John Smith
2018-11-20 3:40 ` Denis Kisselev [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=CY4PR14MB1141B76AC8CD7C2944938FA2A2D90@CY4PR14MB1141.namprd14.prod.outlook.com \
--to=denis@dkisselev.net \
--cc=johnsmith1@riseup.net \
--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).