Book Image

Configuring IPCop Firewalls: Closing Borders with Open Source

Book Image

Configuring IPCop Firewalls: Closing Borders with Open Source

Overview of this book

IPCop is a powerful, open source, Linux based firewall distribution for primarily Small Office Or Home (SOHO) networks, although it can be used in larger networks. It provides most of the features that you would expect a modern firewall to have, and what is most important is that it sets this all up for you in a highly automated and simplified way. This book is an easy introduction to this popular application. After introducing and explaining the foundations of firewalling and networking and why they're important, the book moves on to cover using IPCop, from installing it, through configuring it, to more advanced features, such as configuring IPCop to work as an IDS, VPN and using it for bandwidth management. While providing necessary theoretical background, the book takes a practical approach, presenting sample configurations for home users, small businesses, and large businesses. The book contains plenty of illustrative examples.
Table of Contents (16 chapters)
Configuring IPCop Firewalls
Credits
About the Authors
About the Reviewers
Preface
7
Virtual Private Networks
11
IPCop Support

Firewall Functionality


The Firewall drop-down menu in IPCop contains functionality to configure functions of the firewall itself. Since IPCop's design philosophy is to treat the Green zone as implicitly trusted and downgrade trust from there onwards, there is no egress filtering natively built into IPCop. Instead, your two main choices for configuration here are External Access, which lets you control which ports IPCop will allow in the inbound direction, and Port Forwarding. SeeChapter 9 for more information on setting up a more granular firewall policy, particularly for egress traffic (i.e. traffic traversing from Green to Red).

External Access

All traffic initiated in the Red zone is dropped by the IPCop firewall's rules by default. Almost all traffic coming in through the firewall in response to a request made by a client inside the network (such as a website being served in response to a client sending a get request for the website) is allowed, but in order to allow external hosts...