Date: Tue, 22 May 2018 03:44:26 +0200 From: "Jason A. Donenfeld" <Jason@zx2c4.com> To: Outback Dingo <outbackdingo@gmail.com> Cc: freebsd-ports@freebsd.org, Brady OBrien <brady.obrien128@gmail.com>, WireGuard mailing list <wireguard@lists.zx2c4.com> Subject: Re: WireGuard for FreeBSD Message-ID: <CAHmME9q7Bcigcn5-sEK3=pnuyfDbxxc=HKg4qBCNe_Mj%2BcLjfg@mail.gmail.com> In-Reply-To: <CAKYr3zzm6E_KNXA3acW7QcJWHh1gw3%2BLaxh2fN%2BAS3E0LPn0gg@mail.gmail.com> References: <CAHmME9rJonVbSRHCPy0W7Pr=vmJoMbVTHbGw0C1xwBze4Px7uA@mail.gmail.com> <CAKYr3zzm6E_KNXA3acW7QcJWHh1gw3%2BLaxh2fN%2BAS3E0LPn0gg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 22, 2018 at 2:33 AM, Outback Dingo <outbackdingo@gmail.com> wrote: > to be honest, while it sounds nice, i for one would prefer to see a > kernel module ported to FreeBSD instead of userland > second to that, building a freebsd port of it is not all that hard, > however that being said, it also needs to be accepted > upstream and committed by a ports maintainer, while i can help with > creating it, i still feel a kernel module is a better fit I too would prefer this, and maybe at some point down the line I'll put some real time and effort into porting WireGuard from the Linux kernel to kFreeBSD. But it's not the case that it's "not that hard"; doing so will be a pretty serious undertaking. That's going to take a lot of time. Until that day arrives, what you speak of doesn't exist. What we have instead today is tons of hard work that's gone into bringing a userspace implementation. So please, don't derail the current efforts in favor of an effort that doesn't even exist at the moment.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHmME9q7Bcigcn5-sEK3=pnuyfDbxxc=HKg4qBCNe_Mj%2BcLjfg>