To amplify what vallimar says, the initial iptables script run at boot time is stored in file
/etc/sysconfig/iptables (in "iptables-save" format) and an associated set of parameters in
/etc/sysconfig/iptables-config.
I'm pretty sure that if you apply (by clicking the Apply button) the rules created in the GUI firewall application (system-config-firewall), those rules are indeed saved to
/etc/sysconfig/iptables. I've tested this in F8 - I can't see why it would be different in F9 (it's the same package - based on Lokkit). But, for some unknown reason, the rules are not being saved in your case.
As you probably know, rules can be altered or overwritten at any time using the "iptables" command. Thus, the active rules and saved rules (in
/etc/sysconfig/iptables) may not be the same.
Rather than play with the init variables, IMHO, it's better to manually issue the command to save active rules (in iptables-save format) to
/etc/sysconfig/iptables:
Code:
service iptables save
or to another file:
Code:
iptables-save > {path}/{filename}
When iptables has been correctly configured in your GUI and rules applied, save using one of the above methods and make a backup copy. (If you replace the originals with the backups, remember to check permissions and SELinux context).
You can verify your saved rules against active rules using:
The resulting printout is the active rule set (but it is not in iptables-save format and cannot be used as a script).
You could also use the following (perhaps from within another startup script) to overwrite the current ruleset from a file contaiing your desired rules (in iptables-save format):
Code:
iptables-restore < {path}/{filename}
service iptables restart
Hopefully, this will give you some options to fix the problem.