From: Sascha Grunert <saschagrunert@icloud.com>
To: wireguard@lists.zx2c4.com
Subject: [ANNOUNCE] WireGuard in Rust development started
Date: Tue, 21 Feb 2017 12:48:26 +0100 [thread overview]
Message-ID: <EC598EA9-99F4-4355-BD47-E4BB88E77251@icloud.com> (raw)
Hey folks,
It is great to hear that we can start with the development of the Rust =
version of WireGuard!
The repository can be found here: https://git.zx2c4.com/wireguard-rs/
A GitHub mirror does also exist: =
https://github.com/WireGuard/wireguard-rs
I suggest do use the mailing list and the GitHub features for issue =
handling and discussions.
What do we have for now: I added some initial implementation example =
which uses tokio.rs
(https://tokio.rs) and a custom device handling. You can try it out by =
doing:
```
$ cargo test
$ nc -u 127.0.0.1 8080
Hello world
```
For testing purposes it creates a dummy interface in /tmp where the =
incoming traffic will be
redirected to this interface. Incoming traffic from this interface =
should be sent to the client.
As next steps we can make the server working and add device handling for =
other platforms as
well. :)
Best regards,
Sascha
next reply other threads:[~2017-02-21 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 11:48 Sascha Grunert [this message]
2017-02-21 11:50 ` 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=EC598EA9-99F4-4355-BD47-E4BB88E77251@icloud.com \
--to=saschagrunert@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).