Release Notes: This release fixes the bug where the loopback rules were being QUEUED via the ESTABLISHED,RELATED rule, and so snort-inline boxes would not allow loopback traffic.
Release Notes: This release adds support for Debian Sarge and Red Hat FC[1-3] as "official" distributions for which you can generate init scripts.
Release Notes: All known bugs have been fixed. Support has been added for Debian Sarge and Red Hat FC[1-3] as "official" distributions to work with when generating init scripts. The ability has been added to just install the generated firewall script into /etc/init.d or /etc/pcx-firewall without starting it.
Release Notes: Update to cover the 2.2 config file version. All uses of disabled="false" in the paths, network entries, etc. are now active="true". An XSLT conversion script has been created to convert the version 2.1 config files to version 2.2.
Release Notes: Updated changes needed for the Firewall Frontend 1.6 release. A minor bug in the generated shell script has been fixed.
Release Notes: Many bugfixes and improvements overall. onbeforeunload is used to prevent the loss of data when users click the Back Button, close the window, etc. The boolean select boxes are now checkboxes, which makes the interface much easier to use.
Release Notes: New Service definitions can now be imported from the template config file. Activating a generated firewall script now works as sudo is called.
Release Notes: The edit screens now try to detect when you have made changes and warn you when you are about to do something that would lose those changes. When deleting a Network, Zone, or Service entry, you are now prompted to delete any paths that are using them, thus making it easier to purge entries from the config file without having to manually track them down. There is a new sample config file (dynamic-template.xml) which is a very simplistic case.
Release Notes: DNAT interfaces are now properly selected when editing a Path where the action = DNAT. This fixed the bug where the previous interface was not being selected and the available interfaces were not being updated properly. This is a major issue for anyone using DNAT.