wireguard implementation in progress with zero coordination or communication with wireguard project? can we help?

[K. Macy]

Hi Jason -
I appreciate your enthusiasm, but I can’t count the number of nascent
kernel projects that have come up in discussion over the years and
ultimately come to nothing.

I started by getting the OpenBSD bits to build on FreeBSD. However, the
implementation in Open is not really a very good semantic match for
FreeBSD. So I often have to check what the Linux one is doing as well and
sometimes the NetBSD one. Ultimately, apart from struct definitions, very
little code will be shared between the platforms. I don’t see a whole lot
of benefit to coordination until I can configure a Wireguard interface and
there is at least the possibility of passing packets. At that point,
presumably in the next month or so, I would very much welcome any time you
can spare to audit and provide feedback.

Cheers.

On Tue, Feb 18, 2020 at 06:32 Jason A. Donenfeld <Jason at zx2c4.com> wrote:

> Hi Matthew,
>
> I'm Jason, the lead of the WireGuard project.
>
> Somebody brought it to my attention that Netgate has been sponsoring
> you to write a WireGuard kernel implementation for FreeBSD. What a
> terrific development!
>
> However, this is in fact the first I've heard of such an initiative,
> which is quite surprising and possibly alarming. While I can sort of
> vaguely imagine possible commercial reasons for this from Netgate's
> perspective, I can't imagine that dis-coordination is something
> desirable on the part of FreeBSD. I'd like to find some way we can
> work together on this.
>
> In parallel, the WireGuard project has been working on an
> implementation for OpenBSD's kernel that we intended to eventually
> port to FreeBSD. We're also working on other implementations for other
> platforms as well. It will be interesting to learn if your work is
> "from scratch", or if you've already begun porting the in-progress
> OpenBSD work.
>
> Our goal as a Project is to keep things as uniform and inter-operable
> as possible, to offer the same good experience across platforms.
> Another goal is to keep the security and security-related semantics
> uniform. We view WireGuard as more than just the development of a
> protocol, but rather as a set of implementations that we feel good
> about.
>
> To that end, I was wondering if whatever development has been going on
> for the FreeBSD kernel could begin to work with the WireGuard project.
> Personally, I'd be interesting in auditing the code, reviewing the
> design, matching up configuration semantics, and generally the set of
> things we've done on each platform so far to make sure things going.
> In other words, how can the WireGuard project get involved with this
> great FreeBSD development? How can we begin to coordinate?
>
> Thanks,
> Jason
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>