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

Planning Site-To-Site VPN Topologies


In addition to local services such as those illustrated previously with our IPCop deployment, we may also be using the IPSec software in IPCop to configure a 'site-to-site' VPN to a branch or parent office, business partner, support company, or second site. In such situations, topology planning can become important as a network grows.

It is important, if we have more than one site, to consider exactly how we configure our VPN tunnels in order to provide a balance of service and stability to our clients. In a situation in which two branch offices attached to a main office both contain fileservers synchronizing content with each other, for instance, it would make little or no sense to setup two VPN tunnels from the branch offices to the main office in a 'spoke' topology. The extra hop would, during file transfers, slow down internet connectivity at the main site, and make for slow transfers.

Conversely, if we have many smaller offices with minimal requirements...