Rob, thanks for the detailed explanation of the behaviour. The problem is that some of us who do not need the firewall on (because we have a router with built-in firewall or because it conflicts with a program) still cannot stop ourselves testing the dialog with the unintended result I described.tasmod wrote:Firewallstate.
In firewallstate the code routine for turning the firewall on/off was originally meant to be for testing purposes, I never meant it to 'kill' the firewall program.
The routine uses the firewall programs stop/start feature. (Note:Firewall program, not firewallstate)
The firewall program once installed writes a code line to etc/rc.d/rc.local that checks for the firewall programs file rc.firewall which is created when the firewall program is first run.
Now this will then start the firewall each time at each boot and is independent of the stop/start feature.
To prevent the firewall from restarting at boot I would need to rewrite the code snippet in firewallstate that turns the firewall on/off so that it would erase the rc.firewall file and the rc.local file line for the firewall. This means that to restart the firewall would require a complete re-run of the firewall wizard install routine, hence the entry for this in the firewallstate menu.
I suppose I could add another option in the stop/start small window that would 'kill' the firewall preventing further boot starts. If that's what you wish.
So, yes, an option to 'kill' the firewall would be good.