All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <artyom.h31@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Can WireGuard be adopted for older kernels?
Date: Tue, 05 Jul 2016 01:53:16 +0300	[thread overview]
Message-ID: <1467672796.2967.0@smtp.gmail.com> (raw)
In-Reply-To: <1467672361.2339.0@smtp.gmail.com>

P.S. Sorry for the incorrect From address. It was me, not Jason.

=D0=92 =D0=92=D1=82=D0=BE=D1=80=D0=BD=D0=B8=D0=BA, 5 =D0=B8=D1=8E=D0=BB. 20=
16 =D0=B2 1:46 , Jason A. Donenfeld=20
<artyom.h31@gmail.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
> I'm trying to run WireGuard on a single board computer (ODROID C1).=20
> It's not a problem to modify a board's kernel code, however the chip=20
> manufacturer (Amlogic) is focused on Android and will very unlikely=20
> release a newer kernel for this board.
>=20
> A userspace version is not an option because of a huge performance=20
> penalty of userspace tunnels. It will certainly be slower than IPsec,=20
> and performance is especially important for embedded devices.
>=20
> A small offtopic: why have you chosen to use Rust for a userspace=20
> version and not C or C++? In the latter case you have an option to=20
> reuse some code from the kernel version.
>=20
> =D0=92 =D0=92=D1=82=D0=BE=D1=80=D0=BD=D0=B8=D0=BA, 5 =D0=B8=D1=8E=D0=BB. =
2016 =D0=B2 1:10 , Jason A. Donenfeld=20
> <Jason@zx2c4.com> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB:
>> Hey Artyom,
>>=20
>> I face the same problem as you. I have an Edge Router Lite, and I'd
>> really love to run WireGuard on it, but their proprietary kernel is
>> stuck at 3.10. Major bummer.
>>=20
>> The current plan is to write a userspace version in Rust, that will=20
>> be
>> cross platform and work well on old kernels. No timeline on that
>> though.
>>=20
>> However, I did at one point run wireguard on really old kernels=20
>> during
>> testing. That was before I started using the very nice udp_tunnel_*
>> library inside newer kernels, which then forced the dependency. But
>> when I did do this, it worked. Maybe I'll dust off the ugly old code
>> and hack something horrible together to work on old kernels. On the
>> other hand, this might not really be a great use of time... I don't
>> know.
>>=20
>> What system are you trying to run it on? Maybe if it's the same as=20
>> me,
>> we can both poke Ubnt together to upgrade their kernel...
>>=20
>> Jason
=

  reply	other threads:[~2016-07-04 22:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 21:51 [WireGuard] Can WireGuard be adopted for older kernels? Artyom Aleksyuk
2016-07-04 22:10 ` Jason A. Donenfeld
2016-07-04 22:46   ` Jason A. Donenfeld
2016-07-04 22:53     ` Jason A. Donenfeld [this message]
2016-07-04 23:39       ` Jason A. Donenfeld
2016-07-04 23:42         ` Jason A. Donenfeld
2016-07-04 23:51           ` Artyom Aleksyuk
2016-07-04 23:52             ` Jason A. Donenfeld
2016-07-04 23:54               ` Artyom Aleksyuk
2016-07-06 18:08                 ` 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=1467672796.2967.0@smtp.gmail.com \
    --to=artyom.h31@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.