From: Jonathan Beri <jmberi@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Cortex-m support
Date: Sat, 29 Feb 2020 14:20:05 -0800 [thread overview]
Message-ID: <CANcmUPEcc4TbeSi85nQbG86-nO4mrRE=xCHcid=K8H=UESGVDA@mail.gmail.com> (raw)
In-Reply-To: <CANcmUPEyCiw694-aa32fbLJ5LTd-fMp0D7NtgteqRvLasfmNZQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1678 bytes --]
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!
On Sat, Feb 17, 2018 at 7:39 AM Jonathan Beri <jmberi@gmail.com> wrote:
> Thanks Jason! Do you have a sense of the resource requirements? If that's
> a hard question to answer because of the OS coupling, what about the main
> app minus the OS-owned resources?
>
> For comparison, I'm wondering if wiregaurd can run on a 200mhz cortex m4f,
> with 246KB of ram, with an LwIP ip stack + FreeRTOS. That's the typical IoT
> hardware we target.
>
> On Fri, Feb 16, 2018, 2:21 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
>> Hi Jonathan,
>>
>> Currently it's quite coupled to Linux, but it doesn't have to be that
>> way for ever. Our cross platform implementations are coming along.
>>
>> Jason
>>
>
--
Jonathan Beri
linkedin.com/in/jonathanberi <https://www.linkedin.com/in/jonathanberi/>
[-- Attachment #1.2: Type: text/html, Size: 2760 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-02-29 22:21 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 [this message]
2020-03-01 7:07 ` Jason A. Donenfeld
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='CANcmUPEcc4TbeSi85nQbG86-nO4mrRE=xCHcid=K8H=UESGVDA@mail.gmail.com' \
--to=jmberi@gmail.com \
--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).