Re: WireGuard for FreeBSD

*you* were going to maintain it. >> I only mention it, in hopes all of us might use the --verbose switch in the >> future, in hopes of avoiding this sort of nonsense. :-) :-) >> >> Thanks again, Bernhard! >> >> --Chris >> >> P.S. just in case it w

Re: WireGuard for FreeBSD

ul so in the end that was more like a one day of work effort to get the basic ports. Nevertheless I would still be very happy to increase the bus factor and team up with multiple people to maintain wireguard. I think there will be more work to be done in the near future for wireguard on FreeBSD where

Re: WireGuard for FreeBSD

On 24.05.18 13:07, Jason A. Donenfeld wrote: On Thu, May 24, 2018 at 12:43 PM, Jan Bramkamp wrote: Did I understand correctly that both these ports are userspace implementations and have a similar per packet overhead to OpenVPN and fastd? Indeed they're userspace ports.

Re: WireGuard for FreeBSD

efforts on our porting work which was also what I did expect to happen for wireguard. Well it turned out to be easier than thought and upstream was also very helpful so in the end that was more like a one day of work effort to get the basic ports. Nevertheless I would still be very happy to increas

Re: WireGuard for FreeBSD

finish. > FWIW while you *did* indeed shoot me, and the list a couple of notes. I was > never under the impression you were going to take it so far. Which > *ultimately* > left everyone concerned believing *you* were going to maintain it. > I only mention it, in hopes all of us mi

Re: WireGuard for FreeBSD

On Thu, May 24, 2018 at 9:06 PM, Chris H wrote: > On Thu, 24 May 2018 19:39:22 +0200 "Jason A. Donenfeld" > said > >> Hi Chris, >> >> On Thu, May 24, 2018 at 3:38 PM, Chris H wrote: >> > I should have no trouble introducing

Re: WireGuard for FreeBSD

On Thu, 24 May 2018 19:39:22 +0200 "Jason A. Donenfeld" said Hi Chris, On Thu, May 24, 2018 at 3:38 PM, Chris H wrote: > I should have no trouble introducing Wireguard to the ports system today. I'm not a native fluent speaker of FreeBSDese, but my

Re: WireGuard for FreeBSD

On Thu, 24 May 2018 09:15:28 +0200 "Bernhard Fröhlich" said On Thu, May 24, 2018 at 3:06 AM, Jason A. Donenfeld wrote: > We now have a release, so the full instructions for the packages are: > > 1. wireguard-tools, providing wg(8) and wg-quick(8) > Runtime

Re: WireGuard for FreeBSD

On Thu, May 24, 2018 at 12:43 PM, Jan Bramkamp wrote: > Did I understand correctly that both these ports are userspace > implementations and have a similar per packet overhead to OpenVPN and fastd? Indeed they're userspace ports. Maybe down the line this will be ported to the

Re: WireGuard for FreeBSD

On 24.05.18 09:15, Bernhard Fröhlich wrote: On Thu, May 24, 2018 at 3:06 AM, Jason A. Donenfeld wrote: We now have a release, so the full instructions for the packages are: 1. wireguard-tools, providing wg(8) and wg-quick(8) Runtime dependencies: bash, wireguard-go Buildtime

Re: WireGuard for FreeBSD

On Thu, May 24, 2018 at 3:06 AM, Jason A. Donenfeld wrote: > We now have a release, so the full instructions for the packages are: > > 1. wireguard-tools, providing wg(8) and wg-quick(8) > Runtime dependencies: bash, wireguard-go > Buildtime dependencies: gmake, c compiler, libc

Re: WireGuard for FreeBSD

We now have a release, so the full instructions for the packages are: 1. wireguard-tools, providing wg(8) and wg-quick(8) Runtime dependencies: bash, wireguard-go Buildtime dependencies: gmake, c compiler, libc Build: gmake -C src/tools WITH_WGQUICK=yes Install: gmake -C src/tools

Re: WireGuard for FreeBSD

ate: https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-VERSION.tar.xz _______ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: WireGuard for FreeBSD

Hi Bernhard, Thanks for this. Hopefully this will be good inspiration for Chris' research in making the official package. Chris -- one thing to note is that Bernhard used the "-master" tarballs, which aren't real tarballs and have changing unstable checksums, so you'll of course want to swap

Re: WireGuard for FreeBSD

On Tue, May 22, 2018 at 2:33 AM, Outback Dingo 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

Re: WireGuard for FreeBSD

Hi Chris, Wonderful! Feel free to poke me on IRC -- I'm zx2c4 in #wireguard on Freenode -- if you need any pointers in real time. Some odds and ends that might help: to have a tarball of the latest git master, you can use these links:

Re: WireGuard for FreeBSD

On Mon, 21 May 2018 23:35:45 +0200 "Jason A. Donenfeld" said [cross-posted to the WireGuard mailing list] Hello FreeBSD Ports List, I'm the author of WireGuard [1], a secure network tunnel protocol [2] and a set of implementations of it. It was originally designed for the

WireGuard for FreeBSD

[cross-posted to the WireGuard mailing list] Hello FreeBSD Ports List, I'm the author of WireGuard [1], a secure network tunnel protocol [2] and a set of implementations of it. It was originally designed for the Linux kernel, but we're now beginning to have implementations for other platforms.