From: Jordan Glover <Golden_Miller83@protonmail.ch>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuard Snapshot `0.0.20191205` Available
Date: Fri, 06 Dec 2019 16:23:53 +0000 [thread overview]
Message-ID: <sUhAy9FQoNuL5pe4TIlO25pMeAUxCEvrvj9LPjQ9WauOtxLWfE3Ug9juP6RORXxjLpl6AfV7x5k9i-mkfs-OK1IYx2FcusfU7Ko3uLlcfHM=@protonmail.ch> (raw)
In-Reply-To: <CAHmME9pmhntbNxw9ABjA-krzFARDaV+ZWZhgmWuL9hwfMJUCEA@mail.gmail.com>
On Friday, December 6, 2019 3:52 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> On Fri, Dec 6, 2019 at 4:36 PM Jordan Glover
> Golden_Miller83@protonmail.ch wrote:
>
> > iptables is from Arch Linux iptables-nft package:
> > $ iptables --version
> > iptables v1.8.3 (nf_tables)
>
> Does the segfault happen with the latest version in the git repo?
>
> https://git.zx2c4.com/WireGuard/tree/src/tools/wg-quick/linux.bash
Yes, it still segfaults in the same way as before:
systemd[1]: Stopping WireGuard via wg-quick(8) for wg0...
wg-quick[6528]: [#] iptables -D OUTPUT -o wg0 -j ACCEPT
wg-quick[6528]: [#] ip -4 rule delete table 51820
wg-quick[6528]: [#] ip -4 rule delete table main suppress_prefixlength 0
wg-quick[6528]: [#] ip link delete dev wg0
wg-quick[6528]: [#] resolvconf -d wg0 -f
wg-quick[6620]: [#] iptables-restore -n
audit[6621]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=6621 comm="iptables-restor" exe="/usr/bin/xtables-nft-multi" sig=11 res=1
wg-quick[6620]: /usr/bin/wg-quick: line 29: 6621 Segmentation fault (core dumped) "$@"
kernel: iptables-restor[6621]: segfault at 0 ip 00006e4350496cc9 sp 00007bfae0479dd0 error 4 in libnftnl.so.11.2.0[6e4350494000+18000]
kernel: Code: 15 5c 20 02 00 48 85 c0 74 07 48 89 00 48 89 40 08 48 83 c4 08 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 fd 53 48 83 ec 08 <48> 8b 3f 48 8b 1f 48 39 fd 74 2f 0f 1f 40 00 48 8b 47 08 48 89 43
systemd[1]: wg-quick@wg0.service: Succeeded.
systemd[1]: Stopped WireGuard via wg-quick(8) for wg0.
The "RTNETLINK answers: Address family not supported by protocol"
messages which were caused by lack of ipv6 support in kernel
(AKA weird kernels) was silenced but I think they weren't related
to this problem.
Jordan
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-12-06 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 10:55 Jason A. Donenfeld
2019-12-06 15:10 ` Jordan Glover
2019-12-06 15:20 ` Jason A. Donenfeld
2019-12-06 15:36 ` Jordan Glover
2019-12-06 15:52 ` Jason A. Donenfeld
2019-12-06 16:23 ` Jordan Glover [this message]
2019-12-06 17:35 ` Jason A. Donenfeld
2019-12-11 19:13 ` Jordan Glover
2019-12-11 19:22 ` Jason A. Donenfeld
2019-12-05 10:57 Jason A. Donenfeld
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='sUhAy9FQoNuL5pe4TIlO25pMeAUxCEvrvj9LPjQ9WauOtxLWfE3Ug9juP6RORXxjLpl6AfV7x5k9i-mkfs-OK1IYx2FcusfU7Ko3uLlcfHM=@protonmail.ch' \
--to=golden_miller83@protonmail.ch \
--cc=Jason@zx2c4.com \
--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).