From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Dimitri J. Panagiotou" <dimitri@panagiotou.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: xtables lock at startup?
Date: Sun, 23 Feb 2020 11:58:18 +0100 [thread overview]
Message-ID: <CAHmME9oOq0iVAZZ63N-3yF52pn+D9XEa=dz8hOepq6N8d-e_oQ@mail.gmail.com> (raw)
In-Reply-To: <CAPMuNSoJaLGxTErezypvgh4j6iD9Kj2eh2UtEaGLANqjgwJ6YQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2063 bytes --]
Do what it says; pass the -w option to iptables.
On Sun, Feb 23, 2020, 11:36 Dimitri J. Panagiotou <dimitri@panagiotou.net>
wrote:
> Hi,
>
> Since upgrading to Fedora 31 (5.5), wireguard (latest) does not start
> after rebooting.
> It does start with no problem at all after rebooting, by manually running
> wg-quick.
>
> This is what I get:
> -- Reboot --
> Feb 22 01:19:48 myservername systemd[1]: Starting WireGuard via
> wg-quick(8) for wg0...
> Feb 22 01:19:49 myservername wg-quick[1173]: [#] ip link add wg0 type
> wireguard
> Feb 22 01:19:49 myservername wg-quick[1173]: [#] wg setconf wg0 /dev/fd/63
> Feb 22 01:19:50 myservername wg-quick[1173]: [#] ip -4 address add
> 10.12.182.1/24 dev wg0
> Feb 22 01:19:50 myservername wg-quick[1173]: [#] ip link set mtu 1420 up
> dev wg0
> Feb 22 01:19:50 myservername wg-quick[1173]: [#] mount `10.12.197.1'
> /etc/resolv.conf
> Feb 22 01:19:51 myservername wg-quick[1173]: [#] iptables -A FORWARD -i
> wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o enp2s0 -j MASQUERADE
> Feb 22 01:19:51 myservername wg-quick[1173]: Another app is currently
> holding the xtables lock. Perhaps you want to use the -w option?
> Feb 22 01:19:51 myservername wg-quick[1173]: [#] umount /etc/resolv.conf
> Feb 22 01:19:51 myservername wg-quick[1173]: [#] ip link delete dev wg0
> Feb 22 01:19:51 myservername systemd[1]: wg-quick@wg0.service: Main
> process exited, code=exited, status=4/NOPERMISSION
> Feb 22 01:19:51 myservername systemd[1]: wg-quick@wg0.service: Failed
> with result 'exit-code'.
> Feb 22 01:19:51 myservername systemd[1]: Failed to start WireGuard via
> wg-quick(8) for wg0.
>
> Running
> wireguard-dkms.noarch 1:0.0.20200215-2.fc31
> @jdoss-wireguard
> wireguard-tools.x86_64 1:1.0.20200102-1.fc31
> @jdoss-wireguard
>
> Any idea what's causing this?
>
> Thanks,
> -dimitri
>
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 4509 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-02-23 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 20:35 Dimitri J. Panagiotou
2020-02-23 10:58 ` Jason A. Donenfeld [this message]
2020-02-23 16:49 ` Dimitri J. Panagiotou
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='CAHmME9oOq0iVAZZ63N-3yF52pn+D9XEa=dz8hOepq6N8d-e_oQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=dimitri@panagiotou.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).