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

The Solutions: Proxying and Caching


While use of a proxy isn't a bandwidth-saving measure on its own, it is a feature related to bandwidth control and monitoring. A proxy allows you to monitor, modify, and control requests for web content. You can choose which traffic to log and/or reject as well as modify these requests as they pass through the proxy. Since the proxy sits between the web client and the web server, it can perform some other functions, such as caching.

It's common for users on the same network to access a few of the same websites. This means that every time a user hits the website, they will be downloading all the HTML and images on the page. It would obviously be beneficial for our network if this content was only downloaded once, and then somehow stored to be presented to subsequent clients requesting the same content. Our browsers do that for us at the local level, and so if we access the same page more than once there is a chance our browser has cached a local copy for...