From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Eddie <stunnel@attglobal.net>
Cc: alvind11@hotmail.com, WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wg-quick: syntax error, unexpected saddr
Date: Fri, 3 Jan 2020 16:38:19 +0100 [thread overview]
Message-ID: <CAHmME9r+HM27xhjwDP3q=DJV7KJsvZS__75szHzBE4qHBoXYUg@mail.gmail.com> (raw)
In-Reply-To: <7eb40791-9689-2b3d-bfb0-2299cdf7b07a@attglobal.net>
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 <stunnel@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
next prev parent reply other threads:[~2020-01-03 15:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 5:25 wg-quick: syntax error, unexpected saddr Eddie
2020-01-02 6:22 ` Edward Vielmetti
2020-01-02 7:34 ` Eddie
2020-01-02 8:04 ` Eddie
2020-01-02 20:07 ` Eddie
2020-01-02 20:10 ` Jason A. Donenfeld
2020-01-02 20:43 ` Eddie
2020-01-03 15:38 ` Jason A. Donenfeld [this message]
2020-01-03 16:07 ` Jason A. Donenfeld
2020-01-03 16:22 ` Jason A. Donenfeld
[not found] ` <PU1PR03MB3175D92D59E6C47D12822411D7230@PU1PR03MB3175.apcprd03.prod.outlook.com>
2020-01-03 17:14 ` Jason A. Donenfeld
2020-01-03 20:33 ` Eddie
2020-01-03 20:29 ` Eddie
2020-01-03 20:31 ` Eddie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHmME9r+HM27xhjwDP3q=DJV7KJsvZS__75szHzBE4qHBoXYUg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=alvind11@hotmail.com \
--cc=stunnel@attglobal.net \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).