From: Stefan Agner <stefan@agner.ch>
To: Jason@zx2c4.com
Cc: wireguard@lists.zx2c4.com
Subject: WireGuard recipes for OpenEmbedded
Date: Mon, 03 Apr 2017 00:07:56 -0700 [thread overview]
Message-ID: <a994fb2505af736da73a956fdee94128@agner.ch> (raw)
Hi Jason,
Just posted two recipes which allow building WireGuard using
OpenEmbedded:
http://lists.openembedded.org/pipermail/openembedded-devel/2017-April/112075.html
OE makes it easy to build WireGuard for all sorts of platforms. I
created a quick test VPN between an ARM and 64-bit MIPS machine, seems
to work fine, see
https://blog.printk.io/2017/04/openembedded-recipes-for-wireguard-vpn/
Keep the amazing work, looking forward to see WireGuard upstream :-)
--
Stefan
next reply other threads:[~2017-04-03 7:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 7:07 Stefan Agner [this message]
2017-04-04 13:28 ` Jason A. Donenfeld
2017-05-15 3:33 ` Stefan Agner
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=a994fb2505af736da73a956fdee94128@agner.ch \
--to=stefan@agner.ch \
--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).