On 1/3/2020 9:14 AM, Jason A. Donenfeld wrote:
On Fri, Jan 3, 2020 at 5:43 PM Alvin Darkness wrote:
Unfortunately as slackware 14.2 is a (quite old now) stable release there isnt
much we can do about getting nft past 0.6. A good portion of us slackware
users have moved onto slackware -curren
Let me see if I can install 0.7 without too many dependencies creeping
in. I tried the latest Slackware current build of 0.9, but the
dependencies were getting out of hand.
Cheers.
On 1/3/2020 8:07 AM, Jason A. Donenfeld wrote:
I took a closer look. Indeed the issue is that nft 0.6 is too o
Agreed, way too ugly. :-) Don't do it for me.
Cheers.
On 1/3/2020 8:22 AM, Jason A. Donenfeld wrote:
We could do something like this:
https://git.zx2c4.com/wireguard-tools/commit/?h=jd/nft-version-detection
But that seems pretty ugly and I think I'd rather not.
_
On Fri, Jan 3, 2020 at 5:43 PM Alvin Darkness wrote:
>
> Unfortunately as slackware 14.2 is a (quite old now) stable release there
> isnt much we can do about getting nft past 0.6. A good portion of us
> slackware users have moved onto slackware -current, which is the rolling
> release, as we
We could do something like this:
https://git.zx2c4.com/wireguard-tools/commit/?h=jd/nft-version-detection
But that seems pretty ugly and I think I'd rather not.
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo
I took a closer look. Indeed the issue is that nft 0.6 is too old. Use 0.7+.
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
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/wi
Eddie - what version of nftables does Slackware come with? The output of
`nft -v` should be helpful.
There is a report from stackexchange that nftables at 0.7 gives this error,
but at 0.8.1 or better it's OK. I was not easily able to verify that from
the source code, but it would be where I'd star
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
>
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 t
As a follow up, wireguard-tools v1.0.20200102 also has the issue.
I did think of updating nftables to the latest, but that then started
dragging in too many other updated dependencies I wasn't comfortable
with. So, as nftables currently isn't used on Slack, I renamed the
binary so that wg-qui
Not sure if this helps, or not. But this is the relevant part from a
bash trace:
+ cmd nft -f /dev/fd/63
+ echo '[#] nft -f /dev/fd/63'
[#] nft -f /dev/fd/63
+ nft -f /dev/fd/63
++ echo -n 'add table ip wg-quick-wg0
add chain ip wg-quick-wg0 preraw { type filter hook prerouting priority
-300;
Ha. Even older:
root@The-Tardis:~# nft -v
nftables v0.6 (Support Edward Snowden)
And in reply to a couple of off-list messages:
wireguard-tools-1.0.20191226
There are different reasons for using different VPNs. Can you really
"totally" trust the one that you're using.
Cheers.
On 1/1/2
First time running wireguard as a native client on my Slackware 14.2
system throws this:
root@The-Tardis:~# wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] wg setconf wg0 /dev/fd/63
[#] ip -4 address add 192.168.150.14/32 dev wg0
[#] ip link set mtu 1420 up dev wg0
[#] wg set wg0 fwmark 5
14 matches
Mail list logo
