From: Eddie <stunnel@attglobal.net>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wg-quick: syntax error, unexpected saddr
Date: Fri, 3 Jan 2020 12:33:39 -0800 [thread overview]
Message-ID: <cd6ed339-fac6-8a5f-6d93-abe3d26c860a@attglobal.net> (raw)
In-Reply-To: <CAHmME9oxF4xeHXpirt+iRWQeWknDiteJ7S7WS7fMhfw7nPsHEg@mail.gmail.com>
On 1/3/2020 9:14 AM, Jason A. Donenfeld wrote:
> On Fri, Jan 3, 2020 at 5:43 PM Alvin Darkness <AlvinD11@hotmail.com> 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 wait for Pat to pull the trigger and get slackware 15.0 out. Slackware -current is using nft 0.9.3 at the moment, so no issues there.
>>
>> I can add a caveat to the description/readme on the slackbuilds wireguard-tools page to include something about wg-quick and nft compatibility for 14.2 users.
>>
>> That commit is up to you. If you think an install time solution is better we could just add something to the build script instead.
> Can you just add:
>
> sed -i 's/type -p nft/false/g' src/wg-quick/linux.bash
>
> to your slackbuild before installing? That'll make it fall back to
> iptables always.
Looks like a winner, at least for me, as I do my own builds. Thanks.
Cheers.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-03 20:34 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
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 [this message]
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=cd6ed339-fac6-8a5f-6d93-abe3d26c860a@attglobal.net \
--to=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).