Hey Alex, This is strange. Just builded the package on my PI and it is working as intended. (https://eggiecode.org/wireguard-tools_0.0.20170214-wg1~xenial_armhf.deb ) The PPA build systems screwed the tools package up, looks like it is not running `make install` to the package. See the build log differance in the ppa of armhf and amd64. Greetz, Egbert armhf: https://launchpadlibrarian.net/306379568/buildlog_ubuntu-yakkety-armhf.wireguard_0.0.20170214-wg1~yakkety_BUILDING.txt.gz amd64: https://launchpadlibrarian.net/306379566/buildlog_ubuntu-yakkety-amd64.wireguard_0.0.20170214-wg1~yakkety_BUILDING.txt.gz On 2017-02-19 15:51, Egbert Verhage wrote: > Hey Alex, > > Ow, I never tested the package on armhf. I will give test it tomorrow on > my own Banana Pi 2 and Raspberry pi 2. > > If you are running the image of lemaker on your banana pi, maybe try > first to build the package from the git repo. > > Greetz, > Egbert > > > On 2017-02-19 02:14, Alexander Morlang wrote: >> Hi, >> used the launchpad ppa in xenial on armhf (Banana Pro). >> The wireguard-tools packet installed only /usr/share/doc >> >> Is this a known problem? >> >> I downloaded the >> https://launchpad.net/~wireguard/+archive/ubuntu/wireguard/+files/wireguard-tools_0.0.20170214-wg1~xenial_armhf.deb >> and hat a look with dpkg -c , getting the same result of no binary in the packet. >> >> regards, Alex >> _______________________________________________ >> WireGuard mailing list >> WireGuard@lists.zx2c4.com >> https://lists.zx2c4.com/mailman/listinfo/wireguard > _______________________________________________ > WireGuard mailing list > WireGuard@lists.zx2c4.com > https://lists.zx2c4.com/mailman/listinfo/wireguard