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.

Related Content you might be interested in

Current Title:

Small book image
Configuring IPCop Firewalls: Closing Borders with Open Source
Oct, 2006 | 244 pages
No titles found
Table of Contents (16 chapters)
Configuring IPCop Firewalls
Configuring IPCop Firewalls
Credits
Credits
About the Authors
About the Authors
About the Reviewers
About the Reviewers
Preface
Preface
Free Chapter
1
Introduction to Firewalls
Introduction to Firewalls
An Introduction to (TCP/IP) Networking
The Purpose of Firewalls
The OSI Model
How Networks are Structured
Traffic Filtering
Other Services Sometimes Run on Firewalls
Summary
2
Introduction to IPCop
Introduction to IPCop
Free and Open Source Software
The Purpose of IPCop
The Benefits of Building on Stable Components
The Gap IPCop Fills
Features of IPCop
Virtual Private Networking
Why IPCop?
Summary
3
Deploying IPCop and Designing a Network
Deploying IPCop and Designing a Network
Trust Relationships between the Interfaces
Altering IPCop Functionality
Topology One: NAT Firewall
Topology Two: NAT Firewall with DMZ
Topology Three: NAT Firewall with DMZ and Wireless
Planning Site-To-Site VPN Topologies
Summary
4
Installing IPCop
Installing IPCop
Hardware Requirements
Other Hardware Considerations
The Installation Procedure
Green Interface Configuration
First Boot
Summary
5
Basic IPCop Usage
Basic IPCop Usage
The System Menu
Checking the Status of Our IPCop Firewall
Network Status
Services
Firewall Functionality
Summary
6
Intrusion Detection with IPCop
Intrusion Detection with IPCop
Introduction to IDS
Introduction to Snort
Do We Need an IDS?
How Does an IDS Work?
Using Snort with IPCop
Monitoring the Logs
Log Analysis Options
What to Do Next?
Summary
7
Virtual Private Networks
Virtual Private Networks
What is a VPN?
Summary
8
Managing Bandwidth with IPCop
Managing Bandwidth with IPCop
The Bandwidth Problem
The HTTP Problem
The Solutions: Proxying and Caching
Introduction to Squid
Configuring Squid
Cache Management
Managing Bandwidth without a Cache
Summary
9
Customizing IPCop
Customizing IPCop
Addons
Firewall Addons Server
Common Addons
Summary
10
Testing, Auditing, and Hardening IPCop
Testing, Auditing, and Hardening IPCop
Security and Patch Management
Basic Firewall Hardening
Advanced Hardening
Logfiles and Monitoring Usage
Usage and Denial of Service
Where to Go Next?
Summary
11
IPCop Support
IPCop Support
Support
Summary

Chapter 5. Basic IPCop Usage

Now that we have covered the installation of the IPCop firewall and several situations in which we would want to deploy it, we can discuss how to administer and operate an IPCop firewall. Assuming that the installation has been successful, a default IPCop installation presents us with a web interface. The web interface allows us to configure the firewall via any web browser, and is (by default) enabled only for clients on the Green, internal interface.

The web server runs on port 445 (for HTTPS traffic) by default, although these ports can be altered; the port is different from the commonly used/allocated port (443). It should be noted that accessing the web interface using this port will yield a certificate popup—this results from the use of a self-signed SSL certificate, and can safely be ignored.

The port assignment for HTTPS administration can be changed to any port above 445 using the setreservedports command from the IPCop console or an SSH session, and...

Previous Section
End of Section 1
Next Section