Date: Wed, 15 Jan 2020 13:47:31 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: Peter Libassi <peter@libassi.se> Cc: freebsd-arm@freebsd.org Subject: Re: is wireguard available on arm64 Message-ID: <169812223.9.1579092451897@localhost> In-Reply-To: <8C7FC333-409C-4227-A8F1-52134CF98B4B@libassi.se> References: <8C7FC333-409C-4227-A8F1-52134CF98B4B@libassi.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Peter, Good to hear that it works. For the bugreport. You could try to mail the maintainer of the port. See https://www.freshports.org/net/wireguard/ or https://www.freshports.org/net/wireguard-go/ for the email address of the maintainer. If the maintainer does not reply you can create a bug report at https://bugs.freebsd.org/. Regards, Ronald. Van: Peter Libassi <peter@libassi.se> Datum: dinsdag, 14 januari 2020 17:42 Aan: freebsd-arm@freebsd.org Onderwerp: Re: is wireguard available on arm64 > > I managed to compile (after adding swap space) and install go-devel and the wireguard bits on the RPI3. I also installed the packages on a second RPI3. Set up a wireguard tunnel between the RPI3's using wg-quick and run iperf test. > > iperf direct on the local lan: 94.1 Mbits/sec > iperf over the wireguard tunnel: 71.1 Mbits/sec > > > The wg(8) man page references man pages that do not exist on freebsd, where should I file a bug report? > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > From owner-freebsd-arm@freebsd.org Wed Jan 15 14:47:43 2020 Return-Path: <owner-freebsd-arm@freebsd.org> Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 02DFE1F55D1 for <freebsd-arm@mailman.nyi.freebsd.org>; Wed, 15 Jan 2020 14:47:43 +0000 (UTC) (envelope-from decke@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47yVYB6DFRz4ZXP for <freebsd-arm@freebsd.org>; Wed, 15 Jan 2020 14:47:42 +0000 (UTC) (envelope-from decke@freebsd.org) Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com [209.85.208.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: decke) by smtp.freebsd.org (Postfix) with ESMTPSA id 94791170D3 for <freebsd-arm@freebsd.org>; Wed, 15 Jan 2020 14:47:42 +0000 (UTC) (envelope-from decke@freebsd.org) Received: by mail-lj1-f175.google.com with SMTP id a13so18847538ljm.10 for <freebsd-arm@freebsd.org>; Wed, 15 Jan 2020 06:47:42 -0800 (PST) X-Gm-Message-State: APjAAAVCir4XAlxMWlPzR7ksEl5HUtp0jBU6AIjLCYqQ4rkFIZhyNzXf I4Esb1FvhxEKIkPuznhOPwcj4mRPiM3DzzoDIY9grQ== X-Google-Smtp-Source: APXvYqy0iO43PEcXe8QK+ii76VetWRyfgD+Q27NzZthoBOtiajIx3LG9q74yRl7z91OZ5fSt3JLEvET7IuvWMsgTZ7w= X-Received: by 2002:a2e:7311:: with SMTP id o17mr2094879ljc.197.1579099661132; Wed, 15 Jan 2020 06:47:41 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a19:791c:0:0:0:0:0 with HTTP; Wed, 15 Jan 2020 06:47:40 -0800 (PST) X-Originating-IP: [2001:470:7527:8400:55fd:2544:fdff:f25b] In-Reply-To: <8C7FC333-409C-4227-A8F1-52134CF98B4B@libassi.se> References: <8C7FC333-409C-4227-A8F1-52134CF98B4B@libassi.se> From: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= <decke@freebsd.org> Date: Wed, 15 Jan 2020 15:47:40 +0100 X-Gmail-Original-Message-ID: <CAE-m3X2D3CoB5-=0AhhavoTNqFQF1wp3bnraQKT5hAGbsXY+6Q@mail.gmail.com> Message-ID: <CAE-m3X2D3CoB5-=0AhhavoTNqFQF1wp3bnraQKT5hAGbsXY+6Q@mail.gmail.com> Subject: Re: is wireguard available on arm64 To: Peter Libassi <peter@libassi.se> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>; List-Post: <mailto:freebsd-arm@freebsd.org> List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 15 Jan 2020 14:47:43 -0000 On Tuesday, January 14, 2020, Peter Libassi <peter@libassi.se> wrote: > I managed to compile (after adding swap space) and install go-devel and the wireguard bits on the RPI3. I also installed the packages on a second RPI3. Set up a wireguard tunnel between the RPI3's using wg-quick and run iperf test. > > iperf direct on the local lan: 94.1 Mbits/sec > iperf over the wireguard tunnel: 71.1 Mbits/sec > > > The wg(8) man page references man pages that do not exist on freebsd, where should I file a bugreport. I will have a look and put it on my todo list. If you want you can create a bugreport on bugs.freebsd.org but it's not needed. -- Bernhard Froehlich http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?169812223.9.1579092451897>