BSD

Configuration of DansGuardian

In this section we only cover the basic configuration of DansGuardian. You are also advised to check the documentation on the DansGuardian web site for more information about DansGuardian.

The main DansGuardian configuration file resides in /usr/local/etc/dansguardian/dansguardian.conf. The file is pretty well documented and in this handbook we will only change a few options in order to match our setup.

Installation of DansGuardian

In this chapter of the handbook we will cover the installation and basic configuration of DansGuardian.

In order to install DansGuardian on your FreeBSD system you will need first to fetch the distribution tarball from the DansGuardian Web site and place it in your /usr/ports/distfiles directory.

Once you do that we can continue with the installation of DansGuardian using the FreeBSD Ports Collection.

Configuration of Squid

Squid's main configuration file resides in /usr/local/etc/squid/squid.conf.

Open /usr/local/etc/squid/squid.conf file for editing and do the necessary changes. Most options are self explanatory.

Below you will find a fully working squid.conf file. Please consult the Squid man pages and the example /usr/local/etc/squid/squid.conf.default file for more information about the different options - the file is pretty well documented.

A handbook about the installation and configuration of a Squid transparent proxy server and DansGuardian content filtering system.

Additional information and resources

After reading the handbook you should get an idea of how to automate your FreeBSD environments with Cfengine 3.

Since this handbook cannot cover all the topics and features of Cfengine 3 you are also advised to check the online documentation of Cfengine 3

Managing webservers with Cfengine 3

In this example we will see how we can use Cfengine 3 for managing our Apache webservers.

The purpose of this example is to show you how you can deploy configurations and control daemon processes upon configuration change, and to show you how you can do this with Cfengine 3 we will use the Apache web server as an example.

First we start with defining a new class in our configuration, which we will call webservers.

Package management with Cfengine 3

Another great feature of Cfengine 3 is that you can use it to manage your software distributions.

Cfengine 3 by itself is not a package manager, so you cannot use it to directly manipulate packages on your systems, but instead it can interface with the package managers of the Operating System.

Example Cfengine 3 configurations

If you've followed the handbook by this step, that means that now you have a basic Cfengine 3 policy server and clients already installed and configured.

But let's do something useful with Cfengine 3. In this and the next chapters you will find various Cfengine 3 example configurations, which purpose is only to show you how and what you can do with Cfengine 3.

Client Configuration

Now that we have our Cfengine 3 policy servers configured properly and running, the next thing we are going to do is to configure the clients (agents), that will be controlled via Cfengine 3.

Throughout the handbook we've talked about having different environments in our setup - a TEST one and a production one.

Basic configuration of Cfengine 3

The work directory of Cfengine 3 consists of a number of other directories and files: