Open source firewalls explained

Monday, 30 June 2003, 1:50 PM EST

Free firewalls often suffer from a few of the same class problems:

Weak or missing logging and alerting features
No real-time firewall monitoring capability
Weak or missing graphical user interface
Difficult command prompt-based configuration

These problems all stem from the fact that the software is developed primarily by a single individual or small team rather than by a corporation. Small teams don't have the time or money to spend on ancillary problems like ease of use or sophisticated alerting and logging mechanisms. These features, when present, are nearly always provided by an add-on package developed by a different developer. Free software is developed for people who deeply understand the problem to be solved and the operating system upon which the software runs. With network security being a strong point but ease-of-use being a weakness of these free packages, several companies have built businesses around "finishing" the free firewalls and selling the result. If you look closely, you'll find that under the hood of many of the commercial firewalls a Linux or BSD kernel running IPChains or ipf. For plug-and-play security that may be the better solution, but if you're not afraid to roll your own firewall, then this could be for you.

[ Read more ]

Related items


The price of the Internet of Things will be a vague dread of a malicious world

Regulatory practices assume untrustworthy humans living in a reliable universe. People will be tempted to lie if they think the benefits outweigh the risks, but objects won't.

Weekly newsletter

Reading our newsletter every Monday will keep you up-to-date with security news.

Daily digest

Receive a daily digest of the latest security news.

Thu, Oct 8th