From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Lee Yates <rainmakerraw@icloud.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Very low throughput in *BSDs (but only as a router)
Date: Sun, 22 Jul 2018 00:18:05 +0200 [thread overview]
Message-ID: <20180721221805.GD10598@latitude> (raw)
In-Reply-To: <emf8caba7e-aff8-451d-9ead-efc6ca4ae091@lee-pc>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Hi,
On Fri, Jul 20, 2018 at 08:54:48PM +0000, Lee Yates wrote:
[...]
> To present it visually, in case it makes more sense for the visual
> learners among us:
>
> # Full speed
> Virtual client OS [wg] > virtual router > real home router > WAN > [wg]
> VPN server
>
> # Crippled speed
> Virtual client OS > virtual router [wg] > real router > WAN > [wg] VPN
> server
As far as I understand it, the virtual router OS is based on BSD, right?
Are the virtual client OSes that you tested based on Linux?
If that's the case, then the result is quite expected: There is a fast,
in-kernel implementation for Linux[1], but no fast implementation for BSD.
The implementation for BSD is wireguard-go[2], which hasn't really been
optimized.
Jonathan Neuschäfer
[1]: https://git.zx2c4.com/WireGuard/tree/src
[2]: https://git.zx2c4.com/wireguard-go/about/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-07-21 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 20:54 Very low throughput in *BSDs (but only as a router) Lee Yates
2018-07-21 22:18 ` Jonathan Neuschäfer [this message]
2018-07-22 16:15 ` Re[2]: " Lee Yates
2018-07-23 11:43 ` 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=20180721221805.GD10598@latitude \
--to=j.neuschaefer@gmx.net \
--cc=rainmakerraw@icloud.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).