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 have a Windows 10 on Arm laptop (Lenovo Yoga C630) that I'm
looking to install Wireguard on.
Generally speaking, Windows 10 on Arm runs either arm64 or win32
binaries, but not win64, so I installed the 32-bit x86 version of Wireguard
and the software came up fine.
I created a config to point at
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
> On 2 Jan 2020, at 20:11, Jason A. Donenfeld wrote:
>
> On 12/31/19 1:03 PM, Barry Scott wrote:
>> I had wireguard working but the recent update of somethng has broken it.
>
> Does downgrading fix it? If not, something else is broken. Can you test that
> first?
I already tried that. Dnf sa
Hi,
I hope everyone had an enjoyable festive period.
I have posted this issue on the /r/WireGuard subreddit, and several
Linux people responded that they are also experiencing it. As such I'm
posting here 'properly'.
For a while now, I have noticed that a WG tunnel on my Linux machines
will at s
Further to the below, I have discovered after sending the original
message (typical!) that resolvconf doesn't appear to be being called
correctly, at least on Void.
> resolvconf -a mullvad -m -0 -x
> No file given via stdin
The DNS entry in /etc/resolv.conf stays at the original system DNS and
is
I am experiencing the same issue. For me the problem occurs much less
frequently (one or two times per day) so it wasn't too much trouble to
me. My windows client is configured with 8 peers but most of the time
it communicates with only one of them. There is nothing other than
"Failed to write pack
Interesting bug. According to the man page, the -u should already be
implicit when doing -a, since the contents should be different.
Can you look to see where in the resolvconf script it bails out? Maybe
stick a `set -x` at the top or something similar?
Wintun supports the arm64 kernel. Go supports an arm userland. Ideally
these should match, but they don't right now. It should be possible to
get arm userland talking to the arm64 kernel with some careful struct
poking, but it doesn't sound too pleasant. The best thing to do would
be to get Microso
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
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
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
On 1/2/20 4:58 PM, Barry wrote:
> I already tried that. Dnf says the files needed to downgrade are no longer
> available.
> I did not double check the files in the copr repo folder to see if they can
> be curl’ed.
> I do that check tomorrow.
The old builds got mucked up when we moved to the new
Hey Barry,
Some older versions are building now:
https://copr.fedorainfracloud.org/coprs/jdoss/wireguard/builds/
I have not tested them as I had to make some changes so the old repo
sources to build the src RPMs. Let me know if you run into any issues.
Joe
--
Joe Doss
j...@solidadmin.com
Is "make all" intentionally not provided in wireguard-tools? While you can
do "make" instead of "make all", you need to run make twice to do
the equivalent of "make clean all".
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.co
Thanks for the suggestion.
https://git.zx2c4.com/wireguard-tools/commit/?id=f59f63f4620e89588eaaadb55280e6ca8d8dba1d
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
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.
_
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
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
19 matches
Mail list logo
