[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MW2PR2101MB089257F49E8FAA00CDA63A61BF519@MW2PR2101MB0892.namprd21.prod.outlook.com>
Date: Thu, 13 May 2021 06:19:38 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: "'netfilter-devel@...r.kernel.org'" <netfilter-devel@...r.kernel.org>,
"'netdev@...r.kernel.org'" <netdev@...r.kernel.org>
CC: Stephen Hemminger <sthemmin@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>
Subject: RE: netfilter: iptables-restore: setsockopt(3, SOL_IP,
IPT_SO_SET_REPLACE, "security...", ...) return -EAGAIN
> From: Dexuan Cui
> Sent: Wednesday, May 12, 2021 11:02 PM
BTW, I found a similar report in 2019:
"
https://serverfault.com/questions/101022/error-applying-iptables-rules-using-iptables-restore
I stumbled upon this issue on Ubuntu 18.04. The netfilter-persistent
service failed randomly on boot while working ok when launched manually.
Turned out it was conflicting with sshguard service due to systemd trying
to load everything in parallel. What helped is to setting
ENABLE_FIREWALL=0 in /etc/default/sshguard and then adding sshguard chain
and rule manually to /etc/iptables/rules.v4 and /etc/iptables/rules.v6.
"
The above report provided a workaround.
I think we need a real fix.
Thanks,
-- Dexuan
Powered by blists - more mailing lists