From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: List of commercial WireGuard offerings
Date: Tue, 12 Sep 2017 09:24:04 +0200 [thread overview]
Message-ID: <CAKXLc7cBBpriQ2hHEvERoPWW29EE+DWu0RDSk6tX2qpFNvS45A@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qOEw6Axjv9=XcnrQAm6atZVS4nwXakUBGJunu-eMBmPg@mail.gmail.com>
Great!
On Tue, Sep 12, 2017 at 12:14 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Many people have asked me which companies have commercial for-profit
> WireGuard offerings. Offhand I can think of 3 at the moment:
>
> https://www.mullvad.net/guides/wireguard-and-mullvad-vpn/
> https://www.azirevpn.com/wireguard
>
Those 2 seem to offer software client and/or DIY installation of
wireguard, super!
> https://blackholecloud.com
>
This seems to be more oriented towards non-DIY folks, you get
pre-configured hardware that works only with their service. BTW, the
bigger routers they use are great on their own, I have quite a few
around running OpenWRT or LEDE or something else self-compiled:
https://www.gl-inet.com/ (check the PoE, external antenna options!)
Of course, since they run OpenWRT/LEDE, they do support wireguard.
Cheers,
Kalin.
next prev parent reply other threads:[~2017-09-12 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 22:14 Jason A. Donenfeld
2017-09-12 7:24 ` Kalin KOZHUHAROV [this message]
2017-09-12 8:08 ` Eric Light
2017-09-12 9:11 ` Fredrik Strömberg
2017-09-13 8:59 ` Eric Light
2017-09-16 2:28 ` jugs
2017-09-26 9:06 ` Outback Dingo
2017-09-27 22:51 ` Jason A. Donenfeld
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=CAKXLc7cBBpriQ2hHEvERoPWW29EE+DWu0RDSk6tX2qpFNvS45A@mail.gmail.com \
--to=me.kalin@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;
as well as URLs for NNTP newsgroup(s).