Description of problem: systemctl status iptables.service shows that the service is dead. I can start it by systemctl start iptables.service It is now running. The same thing applies for ip6tables. This applies to the lates updates. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Confirming they were dead here, too. Both are up fine now, after restarting them. However; restarting them kills shorewall and shorewall6 service And restarting shorewall(6), kills iptables and ip6tables firewalld.service was dead since the beginning IIUC, they (firewalld service, too) all have the same purpose; configuring the kernel's firewall tables. Maybe they should never be active at the same time? CC'ing tmb
CC: (none) => marja11, tmbSource RPM: (none) => iptables-1.6.0-2.mga6
They certainly are running at the same time in mga5. Maybe something are changed in how iptables are called in shorewall?
Created attachment 7603 [details] compressed journalctl -b output output includes restarting iptables and later shorewall service, earlier today (see above)
(In reply to Bjarne Thomsen from comment #2) > They certainly are running at the same time in mga5. > Maybe something are changed in how iptables are called in shorewall? (In reply to Bjarne Thomsen from comment #2) > They certainly are running at the same time in mga5. > Maybe something are changed in how iptables are called in shorewall? Thanks, assigning to tmb, then. Maybe this is related: mrt 28 07:07:17 cldrn_64 systemd-sysctl[1042]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file or mrt 28 07:07:17 cldrn_64 systemd-sysctl[1042]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or d mrt 28 07:07:17 cldrn_64 systemd-sysctl[1042]: Couldn't write '0' to 'net/bridge/bridge-nf-call-arptables', ignoring: No such file or (repeated three times) (from the attached journal)
Assignee: bugsquad => tmb
I beleave this has bin fixed.
Not relevant anymore
Then you can close it as you are the reporter
Status: NEW => RESOLVEDResolution: (none) => FIXED