From: Edward Vielmetti <edward.vielmetti@gmail.com>
To: stunnel@attglobal.net
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wg-quick: syntax error, unexpected saddr
Date: Thu, 2 Jan 2020 01:22:43 -0500 [thread overview]
Message-ID: <CAPRZce10tz0KgBUMFcHj09WDvUF_ygpMBQckB-Nebnjk52479g@mail.gmail.com> (raw)
In-Reply-To: <b3fb12ff-969a-9037-ee6f-f8e4b6d91895@attglobal.net>
[-- Attachment #1.1: Type: text/plain, Size: 1865 bytes --]
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 start to look. There was
The nftables 0.8.1 release notes (from 2018) are here:
https://lwn.net/Articles/744480/ and it points to new syntax in this
release.
good luck!
Ed
On Thu, Jan 2, 2020 at 12:27 AM Eddie <stunnel@attglobal.net> wrote:
> 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 51820
> [#] ip -4 route add 0.0.0.0/0 dev wg0 table 51820
> [#] ip -4 rule add not fwmark 51820 table 51820
> [#] ip -4 rule add table main suppress_prefixlength 0
> [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1
> [#] nft -f /dev/fd/63
> /dev/fd/63:5:76-80: Error: syntax error, unexpected saddr
>
> Fairly simple config to connect to my VPS:
>
> [Interface]
> Address = 192.168.150.14/32
> PrivateKey = <Not the key you're looking for>
>
> [Peer]
> PublicKey = <Just being overly paranoid>
> Endpoint = www.xxx.yyy.zzz:51820
> AllowedIPs = 0.0.0.0/0
>
> Not sure what additional information you need collected at this point.
>
> I'm able to connect outbound successfully using NordVPN's version of
> wireguard, but that doesn't use wg-quick, which is where the issue is.
>
> Cheers.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
--
Edward Vielmetti +1 734 330 2465
edward.vielmetti@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 3046 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-03 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 5:25 Eddie
2020-01-02 6:22 ` Edward Vielmetti [this message]
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
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=CAPRZce10tz0KgBUMFcHj09WDvUF_ygpMBQckB-Nebnjk52479g@mail.gmail.com \
--to=edward.vielmetti@gmail.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).