Cortex-m support

Jonathan Beri jmberi at gmail.com
Sat Feb 29 23:20:05 CET 2020


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 at 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 at 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/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20200229/78b6cba2/attachment.html>


More information about the WireGuard mailing list