I'm wondering if anyone would be willing take a look at the following:
https://bugzilla.redhat.com/show_bug.cgi?id=2216972
For me, this issue is reproduced when I load firewalld rules referencing nf tables sets (ipsets) at boot with firewalld and kernel-6.3.9-200.fc38 or kernel-6.3.10-200.fc38
I have my backend set to nftables and am not using direct rules on the affected machines (2 Intel NUCs and a ThinkPad X1 Carbon)
The issue does not occur with kernel-6.3.8-200.fc38 and does not occur if I add the rules referencing ipsets after the initial startup of firewalld is successful.
Thanks in advance for any assistance with this kernel bug.
This seems to be resolved with kernel-6.4.4
On Thursday, June 29, 2023 6:55:26 AM CDT Anthony Messina wrote:
I'm wondering if anyone would be willing take a look at the following:
https://bugzilla.redhat.com/show_bug.cgi?id=2216972
For me, this issue is reproduced when I load firewalld rules referencing nf tables sets (ipsets) at boot with firewalld and kernel-6.3.9-200.fc38 or kernel-6.3.10-200.fc38
I have my backend set to nftables and am not using direct rules on the affected machines (2 Intel NUCs and a ThinkPad X1 Carbon)
The issue does not occur with kernel-6.3.8-200.fc38 and does not occur if I add the rules referencing ipsets after the initial startup of firewalld is successful.
Thanks in advance for any assistance with this kernel bug.
firewalld-users@lists.fedorahosted.org