Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Fredrik Strömberg" <stromberg@mullvad.net>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Is there a way to use wireguard as a non-encrypted VPN?
Date: Tue, 14 Apr 2020 10:53:52 +0200	[thread overview]
Message-ID: <CANTUoeduOe9geMx05JxXdvPkT=FnNnYPuyxhC-XHUgOAPHyMgg@mail.gmail.com> (raw)
In-Reply-To: <9a3401d61035$4d6b5840$e84208c0$@pmfarmwald.com>

On Tue, Apr 14, 2020 at 10:30 AM <mike@pmfarmwald.com> wrote:
>
> I have some older routers that run OpenWRT just fine, but are a bit slow at
> Wireguard (3-5 MBytes/s for SMB transfers) and which are too slow for
> playing HD movies.
> For these routers/uses I don't care about security, I just want a VPN to
> tunnel (thru Comcast, and other ISPs that block lots of ports.)
> If there was a way to use Wiireguard with encryption disabled, I'm pretty
> sure my performance would be closer to 20-50 MB/s which would be more than
> adequate.
> Thanks.
> Mike Farmwald
>

Hi Mike,

No, WireGuard does not and will never support your use case of
disabling encryption.

If you are able to, buy a router that is powerful enough to do
WireGuard at your preferred throughput. Otherwise you would need to
use other encapsulation methods. OpenVPN with hardware AES
acceleration might work (if your routers support that). However
OpenVPN lives in userspace so it needs to do a memory copy from kernel
to userspace for each packet. I'm not sure how the performance will
work out in practice.

If you look at other methods you might want to consider the state of
its maintenance. PPTP code is likely to be very old and unmaintained
for instance. Your router might very well end up hacked.

Cheers,
Fredrik Stromberg

  reply	other threads:[~2020-04-14  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11 19:13 mike
2020-04-14  8:53 ` Fredrik Strömberg [this message]
2020-04-14  9:16 ` Mike O'Connor
2020-04-14 15:02 ` ajs124
2020-04-14 15:16   ` Roman Mamedov

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='CANTUoeduOe9geMx05JxXdvPkT=FnNnYPuyxhC-XHUgOAPHyMgg@mail.gmail.com' \
    --to=stromberg@mullvad.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).