From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jonathan Beri <jmberi@gmail.com>, Mathias <mathias@hall-andersen.dk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Cortex-m support
Date: Sun, 1 Mar 2020 15:07:10 +0800 [thread overview]
Message-ID: <CAHmME9r6Tvc55m1YpX+rdXtx-RO32UgPRTJy4Y76j9E3U2CGeg@mail.gmail.com> (raw)
In-Reply-To: <CANcmUPEcc4TbeSi85nQbG86-nO4mrRE=xCHcid=K8H=UESGVDA@mail.gmail.com>
On Sun, Mar 1, 2020 at 6:20 AM Jonathan Beri <jmberi@gmail.com> wrote:
>
> Hi all,
>
> I'm interested in revisiting the idea of Wireguard on embedded systems. It looks like cross platform implementations have gotten very mature in the past two years. Is it anymore feasible to implement WG in an OS-less ("freestanding") environment where something like a TUN interface doesn't exist? Take one such environment, an RTOS, and the popular open source https://www.zephyrproject.org/. It has a full networking implementation but apps typically use BSD sockets (https://docs.zephyrproject.org/latest/reference/networking/sockets.html) or PPP (https://docs.zephyrproject.org/latest/reference/networking/ppp.html) and network management (https://docs.zephyrproject.org/latest/reference/networking/net_mgmt.html) directly. Also, these implementations are very optimized as they typically run on tiny MCUs (~100 Mhz, 256kb ram.)
>
> I'd be curious to hear y'all's thoughts!
>
It's likely our rust implementation well be well-suited for what you
have in mind.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-03-01 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 20:04 Jonathan Beri
2018-02-16 22:21 ` Jason A. Donenfeld
2018-02-17 15:39 ` Jonathan Beri
2020-02-29 22:20 ` Jonathan Beri
2020-03-01 7:07 ` Jason A. Donenfeld [this message]
2020-03-03 16:14 ` Tony Arcieri
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=CAHmME9r6Tvc55m1YpX+rdXtx-RO32UgPRTJy4Y76j9E3U2CGeg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=jmberi@gmail.com \
--cc=mathias@hall-andersen.dk \
--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).