Hi Eddie, A new Slackware maintainer (CC'd) has been found.
Something to consider with the nft(8) issue, by the way, is not only the version of nft(8), but also the options in your kernel. We check for these ones in Gentoo: https://gitweb.gentoo.org/repo/gentoo.git/tree/net-vpn/wireguard-tools/wireguard-tools-1.0.20200102.ebuild#n39 Jason On Thu, Jan 2, 2020 at 9:43 PM Eddie <stun...@attglobal.net> wrote: > > I don't use those packages for wireguard. I build my own from source. > > But yes, the rest of Slack seems to be stuck in a time-warp. > > Cheers. > > > > On 1/2/2020 12:10 PM, Jason A. Donenfeld wrote: > > On 1/2/20 6:25 AM, Eddie wrote: > > > First time running wireguard as a native client on my Slackware 14.2 > > > system throws this: > > > > So far as I can tell, Slackware hasn't updated its WireGuard since > > 2018: https://slackbuilds.org/repository/14.2/network/WireGuard/ > > > > I've tried several times to contact the maintainers and have not > > received a reply. > > > > It sounds like their kernel and/or nft are similarly bitrotted? > > > > Maybe consider a new distro. > > > > Alternatively, just get rid of nft from your system, and it will > > fallback to using iptables. > > > > Jason > > > > _______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard
