* xtables lock at startup?
@ 2020-02-22 20:35 Dimitri J. Panagiotou
2020-02-23 10:58 ` Jason A. Donenfeld
0 siblings, 1 reply; 3+ messages in thread
From: Dimitri J. Panagiotou @ 2020-02-22 20:35 UTC (permalink / raw)
To: wireguard
[-- Attachment #1.1: Type: text/plain, Size: 1683 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 3722 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: xtables lock at startup?
2020-02-22 20:35 xtables lock at startup? Dimitri J. Panagiotou
@ 2020-02-23 10:58 ` Jason A. Donenfeld
2020-02-23 16:49 ` Dimitri J. Panagiotou
0 siblings, 1 reply; 3+ messages in thread
From: Jason A. Donenfeld @ 2020-02-23 10:58 UTC (permalink / raw)
To: Dimitri J. Panagiotou; +Cc: WireGuard mailing list
[-- 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: xtables lock at startup?
2020-02-23 10:58 ` Jason A. Donenfeld
@ 2020-02-23 16:49 ` Dimitri J. Panagiotou
0 siblings, 0 replies; 3+ messages in thread
From: Dimitri J. Panagiotou @ 2020-02-23 16:49 UTC (permalink / raw)
To: Jason A. Donenfeld; +Cc: WireGuard mailing list
[-- Attachment #1.1: Type: text/plain, Size: 2215 bytes --]
OK, thanks.
On Sun, Feb 23, 2020 at 2:58 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> 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: 5619 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-02-25 0:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-22 20:35 xtables lock at startup? Dimitri J. Panagiotou
2020-02-23 10:58 ` Jason A. Donenfeld
2020-02-23 16:49 ` Dimitri J. Panagiotou
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).