Description of Problem: When running redhat-config-securitylevel-0.9.6-3, I can set the firewall to 'high' or 'medium', but if I attempt to set the firewall to 'no firewall' I get "iptables: No chain/target/match by that name" when I click 'Yes' to accept the change. Version-Release number of selected component (if applicable): How Reproducible: Steps to Reproduce: 1. 2. 3. Actual Results: Expected Results: Additional Information:
The behavior for lokkit has changed. Calling "lokkit -q --disabled" returns: iptables: No chain/target/match by that name Please make lokkit behave like it used to. Running "lokkit --help" still shows --disabled as a valid option.
*** Bug 68820 has been marked as a duplicate of this bug. ***
Created attachment 71865 [details] This patch fixes it for me.
Fixed package is 0.50-16.
Fix confirmed with gnome-lokkit-0.50-16.
*** Bug 72426 has been marked as a duplicate of this bug. ***
*** Bug 72603 has been marked as a duplicate of this bug. ***
Additional comment by knut 2002-08-24 12:59:11 The problem is still present in gnome-lokkit-0.50-17 from rawhide.
Hmm, 'lokkit -q --disabled' works now, but gnome-lokkit is running: iptables -F RH-Lokkit-0-50-INPUT When there is already no firewall, this just gives an error message. But it seems to be functioning correctly---or are you seeing something different? This ought to have stderr redirected to /dev/null I suppose.
Come to think of it, should 'lokkit -q --disabled' be running: iptables -F input or: iptables -F RH-Lokkit-0-50-INPUT ? (Currently it does the former, since I changed it from 'iptables -F INPUT')
Changed it to use: iptables -D INPUT -j RH-Lokkit-0-50-INPUT 2>/dev/null iptables -F RH-Lokkit-0-50-INPUT 2>/dev/null iptables -X RH-Lokkit-0-50-INPUT 2>/dev/null in gnome-lokkit-0.50-18.
Looks good to me.