Rust implementation status

[Jason A. Donenfeld]

Hey Sopium,

Wonderful! I'm traveling now but will review first thing next week.

Please make sure you've implemented https://www.wireguard.io/xplatform/ so
that all implementations can share the same tooling.

Jason

On Mar 13, 2017 00:04, "sopium" <sopium at mysterious.site> wrote:

Hi,

2017-03-05 20:42 GMT+09:00 Sascha Grunert <saschagrunert at icloud.com>:
> Hey folks,
>
> I want to call for participation of the Rust userspace implementation of
WireGuard. The template for the initial implementation was this:
https://www.wireguard.io/xplatform/ and can be found here:
https://git.zx2c4.com/wireguard-rs/.
>
> [......]

I have got an initial working prototype of the WireGuard protocol in
Rust.

The code is at the `wg` branch of `TiTun`[1].

1. https://github.com/sopium/titun/tree/wg

Most of the essential aspects of the WireGuard protocol is
implemented. The missing parts should not be too hard to add.

Only Linux is supported, for the moment.

The implementation is quite fast 🚀, although I haven't spent a lot of
effort in optimization yet. It uses a fixed number of threads to
process packets from UDP socket or TUN device (similar to the other
Haskell impl, nara), and uses fine-grained locking to exploit
parallelism. I get 600Mbps+ to 800Mbps+ throughput and about 0.5ms
latency, between my Haswell Xeon-E3 desktop and a local KVM
instance. It should be able to get even faster with SO_REUSEPORT
sockets and multi-queue TUN devices.

Please review and test.

Regards,
Sopium


_______________________________________________
WireGuard mailing list
WireGuard at lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20170313/6eef265a/attachment.html>